Chuck Rolke created QPID-4727:
---------------------------------

             Summary: C++ Broker ACL rules provide no way to match default 
exchange
                 Key: QPID-4727
                 URL: https://issues.apache.org/jira/browse/QPID-4727
             Project: Qpid
          Issue Type: Bug
          Components: C++ Broker
    Affects Versions: 0.20
            Reporter: Chuck Rolke
            Assignee: Chuck Rolke


ACL rules use 'name=value' formatting. In the case of ACL rule PUBLISH EXCHANGE 
the exchange name must be specified with a name= setting. However, in the case 
of the default exchange the exchange name is blank. There is no way to specify 
a blank exchange name and there is no acceptable workaround.

The proposal is to add keyword *amq.default* to the ACL syntax so that when a 
PUBLISH EXCHANGE rule exchange name is specified with this keyword then the 
run-time rule will actually match a blank exchange name.
{noformat}
 acl allow bob publish exchange name=amq.default routingkey=bobPrivate
 acl deny  all publish exchange name=amq.default routingkey=bobPrivate
{noformat}

Impact assessment:
||Design consideration||Proposed feature||
|Threading model|n/a|
|Memory management|n/a|
|Automated testing approach|easy to test|
|Impact on public API|Adds new keyword to ACL file syntax|
|- Interoperability with implementations in other languages|n/a|
|- Backwards compatibility|No. Old code will try to match literal 'amq.default' 
text|
|Performance implications|Per-message publish exchange lookup tests a bool in 
the rule before checking that the name in the lookup is blank|
|Security implications|New method already protected by ACL|
|Platform support|n/a|
|Logging|no change|
|Monitoring|no change|
|Management|no change|


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to