Description
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:
AMQ222216: Security problem while authenticating: AMQ229031: Unable to validate user from B/192.168.208.3:5672. Username: null; SSL certificate subject DN: unavailable
which btw is immediately shown also as an exception:
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]
both the message and the exception show Username: null, which is not the given username.
On the B side, the error message is:
AMQ222216: Security problem while authenticating: AMQ229031: Unable to validate user from /192.168.208.2:38180. Username: UUUU; SSL certificate subject DN: unavailable
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.
Attachments
Attachments
Issue Links
- relates to
-
ARTEMIS-3191 Cannot use broker-connection mirror with credentials
- Closed
- links to