You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2011/02/25 16:39:38 UTC
[jira] Commented: (AMQ-3191) Add setTrustStore() and setKeyStore()
methods to ActiveMQSslConnectionFactory class
[ https://issues.apache.org/jira/browse/AMQ-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999409#comment-12999409 ]
Timothy Bish commented on AMQ-3191:
-----------------------------------
Think you might have somehow gotten a dup of AMQ-3192 here.
> Add setTrustStore() and setKeyStore() methods to ActiveMQSslConnectionFactory class
> -----------------------------------------------------------------------------------
>
> Key: AMQ-3191
> URL: https://issues.apache.org/jira/browse/AMQ-3191
> Project: ActiveMQ
> Issue Type: Improvement
> Components: JMS client
> Affects Versions: 5.4.2
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Minor
> Labels: ssl
> Fix For: 5.5.0
>
>
> Currently, it is somewhat awkward to use the ActiveMQSslConnectionFactory class, because the only way to set the trust store and the key store is to manipulate KeyManager and TrustManager classes directly. It would be much simpler, if you could simply specify the location of keystore files for the trust store and the key store. E.g. if you added methods like:
> {code}setTrustStore(String)
> setTrustStorePassword(String)
> setKeyStore(String)
> setKeyStorePassword(String){code}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira