qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Godfrey (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-6400) Provide a mechanism to provide a KeyStore itself rather than a file system path to it
Date Mon, 23 Feb 2015 10:46:12 GMT

     [ https://issues.apache.org/jira/browse/QPID-6400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rob Godfrey updated QPID-6400:
------------------------------
    Status: Reviewable  (was: In Progress)

> 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
>            Assignee: Rob Godfrey
>
> 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message