You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2013/04/19 17:15:17 UTC
[jira] [Resolved] (QPID-4739) [Java Broker] complete functionality
to configure multiple key store and trust stores and assign them per-port
[ https://issues.apache.org/jira/browse/QPID-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell resolved QPID-4739.
----------------------------------
Resolution: Fixed
> [Java Broker] complete functionality to configure multiple key store and trust stores and assign them per-port
> --------------------------------------------------------------------------------------------------------------
>
> Key: QPID-4739
> URL: https://issues.apache.org/jira/browse/QPID-4739
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: 0.21
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.22
>
>
> As part of the work in QPID-4390 to overhaul the broker configuration and allow manipulation via the [HTTP] management interface, an intermediate step was made with the SSL configuration by only allowing configuration of a single SSL key store and trust store (and via QPID-4636 a 'peer store') as attributes on the broker itself for use by the AMQP and HTTP(S) ports, with the JMX port relying on the javax.ssl.* properties to configure its SSL key store.
> The desired configuration model, and the way it was represented internally to the broker and externally via the REST api, was for multiple key store and trust stores (which may now be 'peers only' trust stores) to be allowed as child objects of the broker. It was then also intended these would be able to be assigned for use on a per-port basis, including specifying the key store for the JMX port.
> This JIRA will make the necessary changes to transition the brokers SSL configuration to the intended model, updating the web management UI accordingly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org