[
https://issues.apache.org/jira/browse/SLING-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15061960#comment-15061960
]
Bertrand Delacretaz commented on SLING-5355:
--------------------------------------------
A colleague rightly notes that having principal-centric ACL definitions can be
useful as well, so at revision 1720525 I have extended the parser to support
both variants for the "set ACL" statement. The tests found at [1] show more
examples.
{code}
# paths-centric syntax
set ACL on /libs,/apps
remove * for alice, bob
allow jcr:read, jcr:write for fred, wilma
end
{code}
{code}
# principal-centric syntax
set ACL for alice, bob
remove * on /libs, /apps
allow jcr:read on /content
end
{code}
[1]
https://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/acldef/parser/src/test/resources/testcases
> Create service users and ACLs from the provisioning model
> ---------------------------------------------------------
>
> Key: SLING-5355
> URL: https://issues.apache.org/jira/browse/SLING-5355
> Project: Sling
> Issue Type: New Feature
> Components: Service User Mapper
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
>
> As discussed in the "Removing loginAdministrative, how to test that, and
> service username conventions" thread on our dev list [1] we need to be able
> to create service users and set the corresponding ACLs from our provisioning
> model.
> This should be implemented using distinct utility classes, one for the users
> and one for the ACLs, that take simple mini-languages as input. This will
> allow for reusing these utilities in test code for example.
> I have made a suggestion for those mini languages in that thread, will copy
> them here once we agree.
> [1] http://markmail.org/message/kcvuhwfdald2dyuz
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
