[
https://issues.apache.org/jira/browse/AMQ-6418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher L. Shannon resolved AMQ-6418.
-----------------------------------------
Resolution: Fixed
Fix Version/s: 5.15.0
5.14.1
> Peer certificates are not always set when using the auto transports with ssl
> ----------------------------------------------------------------------------
>
> Key: AMQ-6418
> URL: https://issues.apache.org/jira/browse/AMQ-6418
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.14.0
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Fix For: 5.14.1, 5.15.0
>
>
> There are two problems with the auto ssl transport that is causing the peer
> certificates to not always be available and set on the ConnectionInfo object
> during connection. First, for auto+nio+ssl, the auto init transport needs to
> have transport properties applied. This is because the initialization
> transport does the SSL handshake so it needs to know whether or not
> transport.needClientAuth or transport.wantClientAuth is set. Right now these
> properties are not processed so it never gets passed to the SSL socket which
> means none of the protocols have peer certs available over auto+nio+ssl.
> Second, the Stomp transport is not properly setting the peer certs when using
> auto+ssl and not using NIO.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
