Robbie Gemmell updated QPIDJMS-229:
    Summary: allow supplying an SslContext instead of the configuration used to 
create one  (was: Please add back setSslContext() to the ConnectionFactory)

Updated the title to better reflect the ask.

Note that this wasn't 'removed' so much as it was simply never present, with 
the relevant parts of the newer client being implemented for Qpid JMS 0.1.0 
before the change was ever made in the older/other client for Qpid 0.32.

> 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

To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to