[ https://issues.apache.org/jira/browse/QPIDJMS-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202396#comment-16202396 ]
ASF GitHub Bot commented on QPIDJMS-338: ---------------------------------------- Github user asfgit closed the pull request at: https://github.com/apache/qpid-jms/pull/13 > SSL configuration should support setting keyStoreType and trustStoreType > independently > -------------------------------------------------------------------------------------- > > Key: QPIDJMS-338 > URL: https://issues.apache.org/jira/browse/QPIDJMS-338 > Project: Qpid JMS > Issue Type: Improvement > Components: qpid-jms-client > Reporter: Christopher L. Shannon > Priority: Minor > > Currently there is only one configuration option to set the keystore type > when configuration SSL and that option is {{transport.storeType}}. However > sometimes it is useful to be able to set both the keyStoreType and > trustStoreType to different formats. An example might be if the keyStore > format is pkcs11 (a hardware token) and the trust store is still jks or pkcs12 > I'm proposing adding two new configuration options called > {{transport.keyStoreType}} and {{transport.trustStoreType}} that can be set. > The existing option will still be there and if used will just set the both > types to the same thing. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org