Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 18 Oct 2012 05:48:06 +0000 (UTC)
From: "Lionel Cons (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <62741841.62438.1350539286213.JavaMail.jiratomcat@arcas>
In-Reply-To: <123435144.5344.1346140327789.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (AMQ-3996) NIO + SSL: Client certificates are
 null
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AMQ-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478701#comment-13478701 ] 

Lionel Cons commented on AMQ-3996:
----------------------------------

Tim, could you please be a bit more specific in what is needed in terms of configuration?

We use the jaasDualAuthenticationPlugin with two domains configured in login.config (one with SSL, the other one without) and this works fine with stomp+ssl.

Changing the connector to stomp+nio+ssl breaks the authentication (we get java.lang.SecurityException: User name [null] or password is invalid).

Do we need to add configuration bits that are specific to NIO?
                
> 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