Eric Norman created SLING-8117:
----------------------------------
Summary: Add support to read/write of 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, JCR ContentLoader
2.2.6, JCR Base 3.0.4
Reporter: Eric Norman
Assignee: Eric Norman
Fix For: JCR Base 3.0.6, JCR Jackrabbit Access Manager 3.0.4, JCR
ContentLoader 2.2.8
Support for read/write of restrictions on the ACE has not yet been implemented
in the sling jackrabbit.accessmanager REST operations (and elsewhere).
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
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 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. org.apache.sling.jcr.contentloader
a) Changes to the ContentCreator and JsonReader to support reading
restrictions from the JSON and applying them while loading content into the
repository
4. Plus some automated tests and updated documentation...
SLING-6422 appears to have already added support for setting restrictions for
the repoinit style of ACE initialization
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
