activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Posta (JIRA)" <>
Subject [jira] [Commented] (AMQ-3996) NIO + SSL: Client certificates are null
Date Thu, 18 Oct 2012 13:48:03 GMT


Christian Posta commented on AMQ-3996:


I changed the 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:
>             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,,,,
> 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

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:

View raw message