You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Domenico Bruscino (Jira)" <ji...@apache.org> on 2019/09/24 19:03:00 UTC

[jira] [Updated] (ARTEMIS-2503) Improve wildcards for the roles access match

     [ https://issues.apache.org/jira/browse/ARTEMIS-2503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Domenico Bruscino updated ARTEMIS-2503:
---------------------------------------
    Summary: Improve wildcards for the roles access match  (was: Improve the use of wildcards in the key attribute of roles access <match>)

> 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
>
> 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)