[
https://issues.apache.org/jira/browse/SLING-11713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman resolved SLING-11713.
---------------------------------
Resolution: Fixed
No objections were raised, so merged the PR at:
[{{3dd6a2d}}|https://github.com/apache/sling-org-apache-sling-jcr-contentloader/commit/3dd6a2dee2ac5c4c0d9432161552796188eb1361]
> Change ACL json input structure to be less ambiguous for restrictions
> ---------------------------------------------------------------------
>
> Key: SLING-11713
> URL: https://issues.apache.org/jira/browse/SLING-11713
> Project: Sling
> Issue Type: New Feature
> Reporter: Eric Norman
> Assignee: Eric Norman
> Priority: Major
> Fix For: JCR ContentLoader 2.5.4
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> The restriction details in the security:acl contentloader json input can be
> ambiguous in some situations.
> This is the ContentLoader equivalent for what was done for SLING-11243 and
> SLING-11233
> Expected:
> The JSON structure of the security:acl entries should be enhanced to make it
> more clear.
> For example, replace the "granted/denied/restrictions" items with a
> "privileges" structure whose items are the granted or denied privileges.
> Each privilege has a "deny" and/or "allow" child whose value is either true
> (no restrictions) or an array of restrictions + values.
> For example:
> {code:java}
> "security:acl": [
> {
> "principal": "sling123_user",
> "privileges":{
> "jcr:read": {
> "allow": true
> },
> "jcr:write":{
> "allow":{
> "rep:glob":"glob1allow"
> },
> "deny":{
> "rep:glob":"glob1deny"
> }
> }
> }
> }
> ] {code}
>
> The previous syntax should be preserved for backward compatibility.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
