You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2016/12/15 12:42:58 UTC
[jira] [Resolved] (QPIDJMS-229) allow supplying an SslContext
instead of the configuration used to create one
[ https://issues.apache.org/jira/browse/QPIDJMS-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell resolved QPIDJMS-229.
------------------------------------
Resolution: Fixed
Assignee: Robbie Gemmell
Fix Version/s: 0.20.0
> allow supplying an SslContext instead of the configuration used to create one
> -----------------------------------------------------------------------------
>
> Key: QPIDJMS-229
> URL: https://issues.apache.org/jira/browse/QPIDJMS-229
> Project: Qpid JMS
> Issue Type: New Feature
> Affects Versions: 0.11.1
> Reporter: Jason Chan
> Assignee: Robbie Gemmell
> Fix For: 0.20.0
>
>
> In reference to QPIDJMS-183, please add back the implementation of setSslContext().
> The originating ticket which implemented this feature is: QPID-6400. The main reason was to support the use of HSM (https://en.wikipedia.org/wiki/Hardware_security_module) to hold the keystores. This was implemented for 0.32.
> In subsequent releases, this implementation was removed.
> Here is an example of how to use HSM to access the keystore: http://www.pixelstech.net/article/1420699130-Different-types-of-keystore-in-Java----PKCS11. Once you have the keystore you you can initialize the SSLcontext and pass that to the connection factory. As mentioned in QPID-6400, other vendors provide this API as well.
> If possible, please keep the API calls similar to the one in 0.32 as discussed in QPID-6400.
> Thank you!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org