Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-9666

Core Bridge Doesn't Log Authorization Failures

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • AMQ 7.12.3.GA
    • None
    • 1
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      Relatively easy to reproduce.

      1. Create two brokers (configs attached)
      2. Create a second user without send permissions (limited group)
      3. On the first broker, set up a bridge to the second (sample config attached). Use the limited user to configured the bridge
      4. Send messages to the source bridge queue
      5. Messages appear delivering on the queue, but the queue count does not decrease and no exeptions are noted in the broker logs.

      Show
      Relatively easy to reproduce. 1. Create two brokers (configs attached) 2. Create a second user without send permissions (limited group) 3. On the first broker, set up a bridge to the second (sample config attached). Use the limited user to configured the bridge 4. Send messages to the source bridge queue 5. Messages appear delivering on the queue, but the queue count does not decrease and no exeptions are noted in the broker logs.
    • Moderate

      If a core bridge is configured with a user that does not have send permissions on the target broker, messages stay in a delivering state indefinitely and no obvious error is logged on either the source or target broker. If we bump up logging to DEBUG level on the target broker, we can see that the broker is sending back an exception to the bridge producer, but there is no obvious logging at INFO or higher level to indicate the source of the failure.

        1. broker-node2.xml
          13 kB
        2. broker-node1.xml
          13 kB
        3. broker.properties
          0.3 kB

              rhn-support-jbertram Justin Bertram
              rhn-support-dhawkins Duane Hawkins (Inactive)
              Julian Coleman Julian Coleman
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: