[
https://issues.apache.org/jira/browse/AMQ-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478953#comment-13478953
]
Christian Posta commented on AMQ-3996:
--------------------------------------
Tried it out, and it works.
At first I was getting the same errors that Lionel was getting (it got past
that part in JaasCertificateAuthenticationBroker.addConnection() where it was
making sure the TransportContext was an instance of X509Certificate which is
where it was failing previously, but then it would fail at the call to
LoginContext.login() with User name [null] or password invalid error) but then
I changed the user.properties a little bit to match what the client was
presenting in its cert and my tests passed.
> NIO + SSL: Client certificates are null
> ---------------------------------------
>
> Key: AMQ-3996
> URL: https://issues.apache.org/jira/browse/AMQ-3996
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.6.0, 5.7.0
> Reporter: Francesco Romano
> Assignee: Timothy Bish
> Fix For: 5.8.0
>
> Attachments: broker-jaas-ssl-nio.xml, nio+ssl.png,
> NIOSSLTransportWithJaasCertificateAuthBrokerTest.java,
> NIOSSLTransportWithJaasCertificateAuthBrokerTest.java,
> NIOSSLTransportWithJaasCertificateAuthBrokerTest.java, ssl.png
>
>
> If using protocol nio+ssl, the ConnectionInfo transportContext property does
> not contains peer certificates (which are present in the plain tcp ssl
> transport).
> The problem is that in the NIO transport, calling
> sslSession.getPeerCertificates() returns null.
--
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
