Bug 1324721 - Exception raised when Installing into exisiting keystore
Summary: Exception raised when Installing into exisiting keystore
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Installer
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ER3
: 6.3.0
Assignee: Miroslav Sochurek
QA Contact: Dominik Hanak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-07 05:57 UTC by Dominik Hanak
Modified: 2020-03-27 20:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 20:07:50 UTC
Type: Bug


Attachments (Terms of Use)
Installation log (23.54 KB, text/plain)
2016-04-07 05:57 UTC, Dominik Hanak
no flags Details

Description Dominik Hanak 2016-04-07 05:57:58 UTC
Created attachment 1144561 [details]
Installation log

Description of problem:

When I install into keystore that is generated. Installation fails with
exception.


EXCEPTION:
java.lang.Exception: Exception encountered:java.lang.RuntimeException: PBOX000140: Unable to get keystore (/home/hudson/hudson_workspace/workspace/BxMS/BxMS-prod-6.3/installer/bpms-prod-6.3-installer-matrix/423facf8/tests/brms/src/test/resources/vault/vault.keystore)
	at org.jboss.as.security.vault.VaultSession.initSecurityVault(VaultSession.java:194)
	at org.jboss.as.security.vault.VaultSession.startVaultSession(VaultSession.java:212)
	at com.redhat.installer.asconfiguration.ascontroller.ServerCommands.createVaultSession(ServerCommands.java:345)
	at com.redhat.installer.asconfiguration.processpanel.postinstallation.Vault.initVaultSession(Vault.java:40)
	at com.redhat.installer.asconfiguration.processpanel.postinstallation.CustomVault.run(CustomVault.java:33)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at com.izforge.izpack.installer.ProcessPanelWorker$ExecutableClass.run(ProcessPanelWorker.java:755)
	at com.izforge.izpack.installer.ProcessPanelWorker$ProcessingJob.run(ProcessPanelWorker.java:511)
	at com.izforge.izpack.installer.ProcessPanelWorker.runJob(ProcessPanelWorker.java:456)
	at com.izforge.izpack.installer.ProcessPanelWorker.run(ProcessPanelWorker.java:373)
	at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.security.vault.SecurityVaultException: java.lang.RuntimeException: PBOX000140: Unable to get keystore (/home/hudson/hudson_workspace/workspace/BxMS/BxMS-prod-6.3/installer/bpms-prod-6.3-installer-matrix/423facf8/tests/brms/src/test/resources/vault/vault.keystore)
	at org.picketbox.plugins.vault.PicketBoxSecurityVault.init(PicketBoxSecurityVault.java:210)
	at org.jboss.as.security.vault.VaultSession.initSecurityVault(VaultSession.java:191)
	... 13 more
Caused by: java.lang.RuntimeException: PBOX000140: Unable to get keystore (/home/hudson/hudson_workspace/workspace/BxMS/BxMS-prod-6.3/installer/bpms-prod-6.3-installer-matrix/423facf8/tests/brms/src/test/resources/vault/vault.keystore)
	at org.picketbox.plugins.vault.PicketBoxSecurityVault.getKeyStore(PicketBoxSecurityVault.java:691)
	at org.picketbox.plugins.vault.PicketBoxSecurityVault.init(PicketBoxSecurityVault.java:205)
	... 14 more
Caused by: java.io.IOException: Keystore was tampered with, or password was incorrect
	at com.sun.crypto.provider.JceKeyStore.engineLoad(JceKeyStore.java:865)
	at java.security.KeyStore.load(KeyStore.java:1445)
	at org.picketbox.util.KeyStoreUtil.getKeyStore(KeyStoreUtil.java:201)
	at org.picketbox.util.KeyStoreUtil.getKeyStore(KeyStoreUtil.java:151)
	at org.picketbox.plugins.vault.PicketBoxSecurityVault.getKeyStore(PicketBoxSecurityVault.java:688)
	... 15 more


Version-Release number of selected component (if applicable):
6.3.0.ER2 BXMS

How reproducible:
always

Steps to Reproduce:
1. Run Installer 6.3.0.ER2
2. Perform Advanced Configuration and Select "Configure Password Vault"
3. Use exisiting keystore location
4. Watch it fail

Actual results:
Failure of installation.

Expected results:
Installation succeeds


Additional info:
I also had to change password MASKS we use to test this in order for them to match ones that Installer creates, which I never had to do before.

Comment 2 Dominik Hanak 2016-04-14 10:46:54 UTC
Hi Tom,

with BRMS 6.3.0.ER3 everything passes as expected. 

But I can't Verify with BPMS 6.3.0.ER3, see:
https://bugzilla.redhat.com/show_bug.cgi?id=1327135

Comment 3 Dominik Hanak 2016-04-19 08:36:40 UTC
Verified with new 6.3.0.ER3 build.


Note You need to log in before you can comment on or make changes to this bug.