You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2011/08/28 12:17:37 UTC

[jira] [Commented] (APLO-56) Change to a terser configuration scheme for ACL definitions

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

Hiram Chirino commented on APLO-56:
-----------------------------------

Implemented and documented.  Previous apollo configuration files will need to be updated to use the new configuration scheme.  More info at:

http://activemq.apache.org/apollo/versions/1.0-SNAPSHOT/website/documentation/user-manual.html#Authorization

> Change to a terser configuration scheme for ACL definitions
> -----------------------------------------------------------
>
>                 Key: APLO-56
>                 URL: https://issues.apache.org/jira/browse/APLO-56
>             Project: ActiveMQ Apollo
>          Issue Type: Improvement
>          Components: apollo-broker, apollo-dto
>            Reporter: Hiram Chirino
>            Assignee: Hiram Chirino
>             Fix For: 1.0-beta5
>
>
> acls would only need to be defined in the virtual host and broker elements.
> <acl>
>   <allow separator="," kind="some.foo.UnixPrinciple" subject="app1_producers,app1_consumers"  action="create,destroy" object="*" id="app1.*"/>
>   <allow subject="admins" action="*" object="*" id="*"/>
>   <deny subject="admins" action="*" object="*" id="*"/>
> </acl>

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira