[jboss-jira] [JBoss JIRA] (AS7-5855) CLONE - vault script generates identical shared keys when adding multiple passwords in one session

[ https://issues.jboss.org/browse/AS7-5855?page=com.atlassian.jira.plugin.s... ] Geoffrey Bays commented on AS7-5855: ------------------------------------ I am aware of this bug, and have used two interactive sessions to generate two distinct handles to two passwords in the vault. Anyone know of an example of referencing two passwords from the vault in standalone.xml?? I am unable to get this to work. I know, this is not a help forum, but here is my issue below. Or is there a bug here as well?? I need an example of putting two passwords into the vault and then referencing them in standalone.xml. I have referenced the keystore file and password via the vault in the ssl connector line in standalone.xml, and have put the following reference to the truststore and password in as system properties. If I hardcode the unmasked truststore password all works, but even when using two interactive sessions (so that I get a separate handle for the second password), I cannot put two passwords into the vault and get the truststore reference to work. I get IOException: keystore was tampered with of password is incorrect. In standalone.xml: <system-property> <property name="javax.net.ssl.trustStore" value="Path /to/truststore/file" /> <property name="javax.net.ssl.trustStorePassword" value="VAULT::truststore_pass::password::YjdkMDU10TMzTdmy........." /> </system-property> Do I need more lines in the <vault> <vault-option> section to reference the second password? Two vault tags will not parse. Any suggestions or two password example would be most welcome. I have tried referencing the keystore password with the same vault handle since it is the same--does not work. And I have generated vault dat files using a reference to the keystore alone or with a separate reference to the truststore. Neither approach works. Thanks Geoffrey Bays -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira