You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/10/12 17:03:00 UTC
[jira] [Commented] (QPIDJMS-338) SSL configuration should support
setting keyStoreType and trustStoreType independently
[ https://issues.apache.org/jira/browse/QPIDJMS-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202276#comment-16202276 ]
ASF GitHub Bot commented on QPIDJMS-338:
----------------------------------------
GitHub user cshannon opened a pull request:
https://github.com/apache/qpid-jms/pull/13
QPIDJMS-338 - Support setting keyStoreType and trustStoreType
Qpid JMS now support setting the keyStoreType and trustStoreType to
different formats
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cshannon/qpid-jms QPIDJMS-338
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/qpid-jms/pull/13.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #13
----
commit 83b76d36b41c268046ff36c37ffd4b783997fadc
Author: Christopher L. Shannon (cshannon) <ch...@gmail.com>
Date: 2017-10-12T17:00:44Z
QPIDJMS-338 - Support setting keyStoreType and trustStoreType
Qpid JMS now support setting the keyStoreType and trustStoreType to
different formats
----
> 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org