Uploaded image for project: 'ActiveMQ Artemis'
  1. ActiveMQ Artemis
  2. ARTEMIS-3150

wrong username in error message for AMQP connections

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 2.17.0
    • 2.18.0
    • Broker
    • None

    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

        1. login.config
          1 kB
          Erwin Dondorp
        2. brokerB.xml
          9 kB
          Erwin Dondorp
        3. brokerA.xml
          10 kB
          Erwin Dondorp
        4. B.log
          7 kB
          Erwin Dondorp
        5. A.log
          34 kB
          Erwin Dondorp

        Issue Links

          Activity

            People

              clebertsuconic Clebert Suconic
              erwindon Erwin Dondorp
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m