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

Nicolas Peltier resolved SLING-7793.
------------------------------------
       Resolution: Fixed
         Assignee: Nicolas Peltier
    Fix Version/s: pipes 3.0.0

thx Dinesh!

> ACLs pipes
> ----------
>
>                 Key: SLING-7793
>                 URL: https://issues.apache.org/jira/browse/SLING-7793
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: pipes 2.0.2
>            Reporter: Nicolas Peltier
>            Assignee: Nicolas Peltier
>            Priority: Major
>             Fix For: pipes 3.0.0
>
>          Time Spent: 5h
>  Remaining Estimate: 0h
>
> ACLs pipes could be great, with following feature:
> - .allow(userName) (default allow jcr:all on currentResource to userName, can 
> be overriden with jcr:privilege=... property),
> - .deny(userName) (default deny jcr:read on currentResource to userName, can 
> be overriden with jcr:privilege)
> - .acls() will return current resource, with in output bindings array of ACLs 
> mentioning principal, privilege of that resource. If current resource is an 
> authorizable, and if some flag is set to true, then returns ACLs attached to 
> that user in the repository.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to