[ 
https://issues.apache.org/jira/browse/QPIDJMS-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15751262#comment-15751262
 ] 

ASF subversion and git services commented on QPIDJMS-229:
---------------------------------------------------------

Commit 1f2f4aa6565ed465545c87eda3d09540f37afa15 in qpid-jms's branch 
refs/heads/master from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=1f2f4aa ]

QPIDJMS-229: add ability to set an SSLContext via the ConnectionFactory

This facilitates use of hardware security modules, and other cases where
supplying path configuration via the URI options isn't suitable.


> 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to