[ https://issues.apache.org/jira/browse/QPID-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Ross updated QPID-4468: ------------------------------ Fix Version/s: 0.20 > [Java client] restore ability to enable SSL using a connection level option > rather than as a sub-option of each brokerlist entry > -------------------------------------------------------------------------------------------------------------------------------- > > Key: QPID-4468 > URL: https://issues.apache.org/jira/browse/QPID-4468 > Project: Qpid > Issue Type: Improvement > Components: Java Client > Affects Versions: 0.6, 0.8, 0.10, 0.12, 0.14, 0.16, 0.18 > Reporter: Robbie Gemmell > Assignee: Robbie Gemmell > Fix For: 0.20, 0.21 > > > On old client versions it was possible to specify that SSL should be used at > the connection level options. It is now only possible to specify this as part > of the brokerlist sub-options (in addition to much finer-grained control over > the keystores/truststores and certificates etc to be used). If you are just > using the SSL system properties to define they keystore/truststore etc and > have multiple brokers in the brokerlist it is actually more convenient to > specify ssl=true at the connection level. > Restoring this will maintain compatibility for drop-in replacement of old > clients and also help prevent user confiusion resulting from the URL parsers > inability to alert them to the previous ssl configuration going unused. > It will be restored as an ovveride of ssl option in the brokerlist entries. -- 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org