You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Gary Tully (Jira)" <ji...@apache.org> on 2021/12/01 15:05:00 UTC
[jira] [Resolved] (ARTEMIS-3569) Broker balancer based on authenticated user role assignment
[ https://issues.apache.org/jira/browse/ARTEMIS-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved ARTEMIS-3569.
---------------------------------
Resolution: Fixed
> Broker balancer based on authenticated user role assignment
> -----------------------------------------------------------
>
> Key: ARTEMIS-3569
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3569
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: balancer
> Affects Versions: 2.19.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Fix For: 2.20.0
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> following up on ARTEMIS-3365 for the local target path.
> add support for ROLE_NAME as a targetKey.
> Matching one of the Roles of an authenticated principal associated with a connection, accept or reject the connection based on some partition policy based on the role.
> Using the existing regular expression based filter, it is possible to ensure a sub set of roles are associated with a given broker.
> The symmeteric-simple-example that uses the client id key type can be extended to support partitioning on role assignment, the configuration, to use role names that begin with "PARTITION_" and match "PARTITION_FOO" to this broker, would be of the form:
> {code:java}
> <broker-balancer name="symmetric-simple-role">
> <target-key>ROLE_NAME</target-key>
> <target-key-filter>^PARTITION_*</target-key-filter>
> <local-target-filter>^PARTITION_FOO.*</local-target-filter>
> </broker-balancer> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)