You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2014/01/22 19:39:22 UTC
[jira] [Resolved] (AMQNET-467) Strange behaviour on connect with
invalid credentials
[ https://issues.apache.org/jira/browse/AMQNET-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQNET-467.
---------------------------------
Resolution: Fixed
Fixed on trunk and 1.6.x fixes branch
> Strange behaviour on connect with invalid credentials
> -----------------------------------------------------
>
> Key: AMQNET-467
> URL: https://issues.apache.org/jira/browse/AMQNET-467
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: ActiveMQ, NMS
> Affects Versions: 1.6.2
> Reporter: Markus Karolus
> Assignee: Timothy Bish
> Priority: Minor
> Labels: security
> Fix For: 1.6.3, 1.7.0
>
>
> When I try to connect AMQ with invalid credentials I get an EndOfStreamException (Unable to read beyond the end of the stream) instead of an NMSSecurityException (BrokerError: java.lang.SecurityException: User name [***] or password is invalid).
> With the changes for AMQNET-360 the behaviour in the ResponseCorrelator has been changed. With the removing of the exception handling the ExceptionResponse with the Security-Exception will not be handled any more.
> Simple reproduction: TestRestartInvalidCredentialsWithFailover doesn't work
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)