[ https://issues.apache.org/jira/browse/SLING-8118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Norman updated SLING-8118: ------------------------------- Fix Version/s: (was: JCR ContentLoader 2.2.8) JCR ContentLoader 2.3.0 > Add support to set ACE restrictions from contentloader > ------------------------------------------------------ > > Key: SLING-8118 > URL: https://issues.apache.org/jira/browse/SLING-8118 > Project: Sling > Issue Type: New Feature > Affects Versions: JCR ContentLoader 2.2.6 > Reporter: Eric Norman > Assignee: Eric Norman > Priority: Major > Fix For: JCR ContentLoader 2.3.0 > > > Support for write of restrictions on the ACE has not yet been implemented in > the sling jcr.contentloader bundle. > > However it looks like adding support for 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.contentloader > a) Changes to the ContentCreator and JsonReader to support reading > restrictions from the JSON and applying them while loading content into the > repository > 3. 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)