Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Tue, 23 Oct 2012 15:27:12 +0000 (UTC)
From: "Timothy Bish (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <1116257983.16269.1351006032957.JavaMail.jiratomcat@arcas>
In-Reply-To: <522223122.16224.1351005432073.JavaMail.jiratomcat@arcas>
Subject: [jira] [Assigned] (AMQ-4126) stomp+nio+ssl +
 jaasDualAuthenticationPlugin + certificate authentication fails
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMQ-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish reassigned AMQ-4126:
---------------------------------

    Assignee: Timothy Bish
    
> stomp+nio+ssl + jaasDualAuthenticationPlugin + certificate authentication fails
> -------------------------------------------------------------------------------
>
>                 Key: AMQ-4126
>                 URL: https://issues.apache.org/jira/browse/AMQ-4126
>             Project: ActiveMQ
>          Issue Type: Bug
>            Reporter: Massimo Paladin
>            Assignee: Timothy Bish
>         Attachments: AMQ4126.tgz
>
>
> Hello,
> ActiveMQ's trunk currently fails for the current use case:
> - server: stomp+nio+ssl connector + jaasDualAuthenticationPlugin
> - client: connecting to the server and expecting private certificate authentication
> Unit test reproducing the problem provided.
> {noformat}
> 2012-10-23 17:13:01,207 [MQ NIO Worker 4] - WARN  ProtocolConverter              - Exception occurred processing: 
> CONNECT
> ^@: java.lang.SecurityException: User name [null] or password is invalid.
> 2012-10-23 17:13:01,210 [MQ NIO Worker 4] - WARN  Transport                      - Transport Connection to: tcp://128.141.156.34:59500 failed: java.io.IOException: User name [null] or password is invalid.
> {noformat}

--
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