[
https://issues.apache.org/jira/browse/QPID-6400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333587#comment-14333587
]
ASF subversion and git services commented on QPID-6400:
-------------------------------------------------------
Commit 1661729 from [~godfrer] in branch 'qpid/branches/0.32'
[ https://svn.apache.org/r1661729 ]
QPID-6400 : Merge of r1661142 to 0.32 branch
> 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: JMS AMQP 1.0 Client
> Affects Versions: 0.30
> Reporter: Anand Gopinath
> Assignee: Keith Wall
>
> 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]
