[
https://issues.apache.org/jira/browse/ARTEMIS-2503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16958184#comment-16958184
]
ASF subversion and git services commented on ARTEMIS-2503:
----------------------------------------------------------
Commit 0ac605740eda4a11dfa29150da343557435d5db7 in activemq-artemis's branch
refs/heads/master from brusdev
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=0ac6057 ]
ARTEMIS-2503 Improve wildcards for the authorisation key attributes
Improve wildcard support for the key attribute in the roles access
match element and whitelist entry element, allowing prefix match for
the mBean properties.
> Improve wildcards for the roles access match
> --------------------------------------------
>
> Key: ARTEMIS-2503
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2503
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Domenico Bruscino
> Priority: Major
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> Please improve wildcard support for the key element in the roles access
> <match> element.
> ATMÂ you can NOT apply a restriction across a set of queue instances starting
> with the same prefix (like below):
> {code:java}
> <match domain="org.apache.activemq.artemis" key="queue=my*">
> <access method="list*" roles="group2"/>
> <access method="get*" roles="group2"/>
> ...
> </match>{code}
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
