[
https://issues.apache.org/jira/browse/QPID-7273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall resolved QPID-7273.
------------------------------
Resolution: Fixed
> The same JVM property names are used on client and broker sides for setting
> protocol and cipher suite white and black lists
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-7273
> URL: https://issues.apache.org/jira/browse/QPID-7273
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker, Java Client, Java Common
> Affects Versions: qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2,
> qpid-java-6.0.3, qpid-java-6.1
> Reporter: Alex Rudyy
> Assignee: Keith Wall
> Fix For: qpid-java-6.1
>
>
> Both Java Client and Java Broker user JVM properties
> "qpid.security.tls.protocolWhiteList" and
> "qpid.security.tls.protocolBlackList" to configure TLS protocols white list
> and black list accordingly. JVM properties for setting cipher suites (
> "qpid.security.tls.cipherSuiteWhiteList" and
> "qpid.security.tls.cipherSuiteBlackList" ) are utilized by both components as
> well.
> However, Java Broker expects JSON formatted values for protocol and cipher
> suite white and black lists whilst Java Client expects comma separated values
> for protocol and cipher suite white and black lists. In case when both Java
> Broker and Client run in the same JVMs setting of protocol and cipher suite
> white and black lists would be a problem as depending from format in use
> either Broker or Client would have incorrectly set white and black lists.
> In order to resolve this problem we need to use different JVM property names
> for Broker and Client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
