-
Story
-
Resolution: Done
-
Major
-
AMQ 7.2.2.GA
-
None
-
4
-
Documentation (Ref Guide, User Guide, etc.)
-
-
+
-
Verified in a release
-
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.
- is cloned by
-
ENTMQBR-3212 [Documentation: [AMQ7, jmx rbac] allow use of wildcards in the key attribute of <match>
- Closed
- relates to
-
ENTMQBR-2472 Support or document per-role control and monitoring of individual destinations in the console
- New