[jira] [Created] (QPID-8488) [Broker-J] Enhance ACL rule with multi-value properties

["Marek Laca (Jira)" <ji...@apache.org>]

Marek Laca created QPID-8488:
--------------------------------

             Summary: [Broker-J] Enhance ACL rule with multi-value properties
                 Key: QPID-8488
                 URL: https://issues.apache.org/jira/browse/QPID-8488
             Project: Qpid
          Issue Type: Improvement
          Components: Broker-J
            Reporter: Marek Laca


We are using an extensive set of the ACL rules. Our set contains a lot of rules that differ only in single value. For example:
{code:none}
ACL ALLOW CON_USER CONSUME QUEUE name="broadcast.ABC.Public"
ACL ALLOW CON_USER CONSUME QUEUE name="broadcast.ABC.Private"
ACL ALLOW CON_USER CONSUME QUEUE name="broadcast.ABC.Repeat"
ACL ALLOW CON_USER CONSUME QUEUE name="response.ABC"
ACL ALLOW CON_USER CONSUME QUEUE name="error.ABC"
{code}
These rules differ only in "name" property, hence if the "name" was a multi-value property then it would allow us to merge the rules into one:
{code:none}
ACL ALLOW CON_USER CONSUME QUEUE name=[broadcast.ABC.Public, broadcast.ABC.Private, broadcast.ABC.Repeat, response.ABC, error.ABC]
{code}
The multi-value functionality would decrement the amount of our rules substantially and improves the broker throughput.

*Proposed solution:*

We could set up multiple possible values as a comma separated list in brackets. The multi-values property can be implemented as the compressed prefix tree that checks an input string in linear time.
 This task depends on the [QPID-8487|https://issues.apache.org/jira/browse/QPID-8487] because the refactoring of [QPID-8487|https://issues.apache.org/jira/browse/QPID-8487] clears the way for an effective implementation.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org