[
https://issues.apache.org/jira/browse/ARTEMIS-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17304890#comment-17304890
]
Stephen Baker commented on ARTEMIS-3150:
----------------------------------------
I'm hitting an issue that looks somewhat similar to this, but has farther
reaching consequences - with valid credentials mirroring isn't working;
described here:
[https://stackoverflow.com/questions/66643177/how-to-authenticate-session-used-for-broker-connections-in-artemis]
Do you think it deserves it's own issue, or it's another consequence of this?
> wrong username in error message for AMQP connections
> ----------------------------------------------------
>
> Key: ARTEMIS-3150
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3150
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.17.0
> Reporter: Erwin Dondorp
> Priority: Minor
> Attachments: A.log, B.log, brokerA.xml, brokerB.xml, login.config
>
>
> I'm connecting independent brokers A and B using the {{broker-connections}}
> mechanism. A connects to B.
> Using URI, NAME, USER and PASSWORD attributes. The password is wrong on
> purpose.
> On the A side, the error message is:
> {noformat}
> AMQ222216: Security problem while authenticating: AMQ229031: Unable to
> validate user from B/192.168.208.3:5672. Username: null; SSL certificate
> subject DN: unavailable
> {noformat}
> which btw is immediately shown also as an exception:
> {noformat}
> AMQ229031: Unable to validate user from shore01/192.168.208.3:5672. Username:
> null; SSL certificate subject DN: unavailable:
> ActiveMQSecurityException[errorType=SECURITY_EXCEPTION message=AMQ229031:
> Unable to validate user from B/192.168.208.3:5672. Username: null; SSL
> certificate subject DN: unavailable]
> {noformat}
> both the message and the exception show {{Username: null}}, which is not the
> given username.
> On the B side, the error message is:
> {noformat}
> AMQ222216: Security problem while authenticating: AMQ229031: Unable to
> validate user from /192.168.208.2:38180. Username: UUUU; SSL certificate
> subject DN: unavailable
> {noformat}
> this message shows the correct username.
> So the error message that gets returned from B to A is not the same and has
> less useful information.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
