[
https://issues.apache.org/jira/browse/SLING-8117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman resolved SLING-8117.
--------------------------------
Resolution: Fixed
Fixed at:
https://github.com/apache/sling-org-apache-sling-jcr-jackrabbit-accessmanager/commit/3dc7c2fb05926e60f3699a0c2f0c337264a82637
> Add support to read/write ACE restrictions from REST
> ----------------------------------------------------
>
> Key: SLING-8117
> URL: https://issues.apache.org/jira/browse/SLING-8117
> Project: Sling
> Issue Type: New Feature
> Affects Versions: JCR Jackrabbit Access Manager 3.0.2
> Reporter: Eric Norman
> Assignee: Eric Norman
> Priority: Major
> Fix For: JCR Jackrabbit Access Manager 3.0.4
>
>
> Support for read/write of restrictions on the ACE has not yet been
> implemented in the sling jackrabbit.accessmanager REST operations.
>
> However it looks like adding support for read/write of ACE restrictions
> would not be too difficult and it looks like it could be useful to the
> community.
>
> It looks like changes would be needed in a few bundles, specifically these:
>
> 1. org.apache.sling.jcr.base ( see SLING-8139 )
> a) Changes to the AccessControlUtil addEntry/replaceAccessControlEntry
> methods to support passing in and processing of restrictions
> 2. org.apache.sling.jcr.jackrabbit.accessmanager
> a) ModifyAce - changes to process posted "restriction" parameters to be
> set
> b) GetAcl/GetEffectiveAcl servlets - changes to return the declared
> restriction values in the returned JSON
> c) PrivilegesInfo - add methods to read the declared restrictions to be
> used from scripts who are interested in such things
> 3. Plus some automated tests and updated documentation...
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
