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

Chuck Rolke resolved QPID-3892.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 0.19

Fixed by r1361678 and r1362014.

Note that the fix does not use regex. Instead Acl code now uses the same Topic 
Exchange match code that the broker runtime uses. This avoids introducing new 
syntax (regex) in the Acl file and lets it use naturally expressed topic 
exchange syntax. Also this fix adds no new module to any distributions.
                
> ACLs shall support full regular 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
>            Assignee: Chuck Rolke
>              Labels: features
>             Fix For: 0.19
>
>         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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to