[jira] [Resolved] (ARTEMIS-567) broker logs erroneous 'user name is null' message during successful AMQP connection

["Justin Bertram (JIRA)" <ji...@apache.org>]

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

Justin Bertram resolved ARTEMIS-567.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.4.0

This should be fixed via eb785b419495562e0a11f2f668dd96c553457430.

> broker logs erroneous 'user name is null'  message during successful AMQP connection
> ------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-567
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-567
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: AMQP
>    Affects Versions: 1.3.0
>            Reporter: Robbie Gemmell
>            Assignee: Justin Bertram
>            Priority: Minor
>             Fix For: 1.4.0
>
>
> I noticed testing the 1.3.0 RC that upon every successful login with an AMQP 1.0 client, where the client has actually provided a valid user/pass, the broker logs an erroneous info message that it couldnt validate the user because the user name is null:
> {noformat}
> 10:29:49,470 INFO  [org.apache.activemq.artemis.spi.core.security.ActiveMQJAASSecurityManager] Couldn't validate user: user name is null
> {noformat}
> In contrast, then actually trying to log in with an incorrect user name (in this case called "wrong") gives both the same erroneous message about null user and then another message that the user didnt exist:
> {noformat}
> 10:38:33,160 INFO  [org.apache.activemq.artemis.spi.core.security.ActiveMQJAASSecurityManager] Couldn't validate user: user name is null
> 10:38:33,256 INFO  [org.apache.activemq.artemis.spi.core.security.ActiveMQJAASSecurityManager] Couldn't validate user: User does exist
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)