[
https://issues.apache.org/jira/browse/QPID-6400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329065#comment-14329065
]
Rob Godfrey edited comment on QPID-6400 at 2/20/15 3:47 PM:
------------------------------------------------------------
I've added get/setSslContext to the ConnectionFactoryImpl. If you explicitly
set the SslContext then it will override any other settings for the SslContext
made through setters or through the initial URL.
Is this sufficient to meet you issue? If so I could ask for it to be merged to
the 0.32 branch so it can make it out for that release.
was (Author: rgodfrey):
I've added get/setSslContext to the ConnectionFactoryImpl. If you explicitly
set the SslContext then it will override any other settings for the SslContext
made through setters or through the initial URL.
Is this sufficient to meet you issue? If so I can could for it to be merged to
the 0.32 branch so it can make it out for that release.
> 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: [email protected]
For additional commands, e-mail: [email protected]
