[
https://issues.apache.org/jira/browse/AMQ-6665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986373#comment-15986373
]
ASF subversion and git services commented on AMQ-6665:
------------------------------------------------------
Commit 57795bafcea290c6879bb288822435c480a9212d in activemq's branch
refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=57795ba ]
[AMQ-6665] - check for peercerts is now on tcp transport such that the bridge
connection info can have the correct context
> certificate-based authentication on network bridge fails for nio+ssl protocol
> -----------------------------------------------------------------------------
>
> Key: AMQ-6665
> URL: https://issues.apache.org/jira/browse/AMQ-6665
> Project: ActiveMQ
> Issue Type: Bug
> Components: networkbridge
> Affects Versions: 5.14.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.15.0
>
>
> client certificate authentication works in the following scenario:
> {code}
> Broker A
> ...
> <jaasDualAuthenticationPlugin
> configuration="activemq"
> sslConfiguration="CertLogin" />
> ...
> <transportConnector name="sslTransportConnector"
> uri="ssl://0.0.0.0:61618?needClientAuth=true&wantClientAuth=true"/>
> {code}
> Broker B
> {code}
> ...
> networkConnector uri="static://(ssl://localhost:61618)"
> name="myNetworkConnector" duplex="true" consumerTTL="2" messageTTL="100"
> dynamicOnly="false">
> ...
> {code}
> But if you change the transport to nio+ssl, the network connector fails with
> the following message:
> {code}
> INFO | Stopping vm://localhosta#0 because Failed with SecurityException: User
> name [null] or password is invalid.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
