[
https://issues.apache.org/jira/browse/QPID-6400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14327955#comment-14327955
]
Anand Gopinath commented on QPID-6400:
--------------------------------------
The code I was using called
{{javax.jms.ConnectionFactory#createConnection(java.lang.String,
java.lang.String)}} which is implemented by
{{org.apache.qpid.amqp_1_0.jms.impl.ConnectionFactoryImpl#createConnection(java.lang.String,
java.lang.String)}}. I suppose I can change that to create the ConnectionImpl
directly rather than going through the factory. Unless you have a better
suggestion. Thanks!
> Provide a mechanism to provide a KeyStore itself rather than a file system
> path to it
> -------------------------------------------------------------------------------------
>
> Key: QPID-6400
> URL: https://issues.apache.org/jira/browse/QPID-6400
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker, Java Client
> Affects Versions: 0.30
> Reporter: Anand Gopinath
>
> When setting up SSL to communicate to ActiveMQ using the Java Client for
> example, a keystore, truststore, keystore password, truststore password are
> needed.
> Is there a mechanism by which a KeyStore can be set rather than created via
> via paths to config files? In an HSM environment, there isn't really a way to
> put a path to a keystore/truststore.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
