[ 
https://issues.apache.org/jira/browse/QPID-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13226112#comment-13226112
 ] 

Pavel Moravec commented on QPID-3892:
-------------------------------------

A comment to the description (did not know formatting syntax that expanded 
asterisks):

Current ACLs can't authorize just to <anything>.sports and to usa.<anything>
                
> ACLs shall support full regural expressions in property values
> --------------------------------------------------------------
>
>                 Key: QPID-3892
>                 URL: https://issues.apache.org/jira/browse/QPID-3892
>             Project: Qpid
>          Issue Type: Improvement
>          Components: C++ Broker
>    Affects Versions: 0.14
>            Reporter: Pavel Moravec
>              Labels: features
>         Attachments: ACLs-full-regexp.patch
>
>
> Currently ACL syntax supports in a property value either direct match 
> ("name=RequestQueue") or a substring match ("name=tmp.*").
> That is not sufficient when authorizing access to topics. One particular 
> example: amq.topic exchange receives messages with keys usa.sports, usa.news, 
> europe.sports and europe.news. Currently we can not authorize access just to 
> topics *.sports and to usa.* 
> As there exist different use cases where regular expressions are required in 
> a, it is meaningful to support (full) regular expressions in ACL property 
> values.
> Since qpid C++ broker already relies on boost libraries a lot, I suggest (in 
> a patch proposed) using boost::regex library.
> I tested the attached patch on Fedora, not sure if other Linux distributions 
> are familiar with the change in Makefile.am.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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