[
https://issues.apache.org/jira/browse/AMQ-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479004#comment-13479004
]
Christian Posta commented on AMQ-3996:
--------------------------------------
Lionel,
I changed the user.properties file referenced by my login.conf to match the
client with what was in the cert.
client=CN=client, OU=activemq, O=apache
#client=CN=client, OU=activemq, O=apache, L=Unknown, ST=Unknown, C=Unknown
Now that I think about it, I should have verified the client's cert to make
sure it wasn't indeed passing the data in the commented out (second) line and
that the SSL code only saw the first line.
> 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
