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

[AMQ7, jmx rbac] allow use of wildcards in the key attribute of <match>

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • AMQ 7.6.0.CR1
    • AMQ 7.2.2.GA
    • broker-core
    • None
    • AMQ Broker 3819, AMQ Broker 4219

      Please add wildcard support for the key element in the <match> element.

      We can restrict access to a specific queue instance using JMX RBAC with the "queue=my.test"

      <match domain="org.apache.activemq.artemis" key="queue=my.test">
            <access method="list*" roles="group2"/>
            <access method="get*" roles="group2"/>
            ...
       </match>
      
      

      However wild cards do NOT seem to work in the key field. So you can NOT apply a restriction across a set of queue instances starting with the same prefix (like below):

      <match domain="org.apache.activemq.artemis" key="queue=my*">
            <access method="list*" roles="group2"/>
            <access method="get*" roles="group2"/>
            ...
       </match>
      
      

      If queues are created dynamically and only a queue name "prefix" is known in advance; JMX RBAC cannot be used to restrict access in this case.

              dbruscin Domenico Francesco Bruscino
              rhn-support-pfox Patrick Fox (Inactive)
              Tiago Bueno Tiago Bueno
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: