Uploaded image for project: 'ActiveMQ'
  1. ActiveMQ
  2. AMQ-5814

Wrong with role-based authorization when using right permission

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 5.10.0, 5.10.2, 5.11.0, 5.11.1
    • Fix Version/s: 5.11.2, 5.12.0
    • Component/s: Broker, MQTT
    • Labels:
      None
    • Environment:

      Unix, Windows

    • Regression:
      Unit Test Broken

      Description

      Since version 5.10, the problem has been caused by broker. It was behaving wrong with role-based authorization. I have configured right SimpleAuthorization plugin but no luck.

      I guess it has problem from AMQ-5160

      Here my test cases on github, please review and let me know if you have any questions: https://github.com/hongphu8790/activemq/tree/master/mqtt-authorization-test

      Project test-case descriptions:

      • Using debug mode for broker to view detail
        problem.
      • Repeat with pom.xml file
        + With AMQ 5.9.1 (it will pass all test cases)
        + With AMQ >= 5.10.0 (it will pass only test cases with using publisher have super permission

      Here my log occurred when the test case failed:

      Log debug mode - activemq.log
      2015-05-29 10:30:24,746 | DEBUG | AbstractRegion                 | Subscription denied for TopicSubscription: consumer=ID:XXXXXX-50828-1432870224218-2:2:-1:1, destinations=0, dispatched=0, delivered=0, matched=0, discarded=0 to destination topic://dcu.id: User publisher is not authorized to read from: topic://dcu.id
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                tabish121 Timothy Bish
                Reporter:
                hongphu8790 PhuNH5-VTICT
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: