You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@sling.apache.org by ss...@apache.org on 2017/06/14 07:51:35 UTC

svn commit: r1798657 - /sling/site/trunk/content/documentation/bundles/content-loading-jcr-contentloader.mdtext

Author: sseifert
Date: Wed Jun 14 07:51:34 2017
New Revision: 1798657

URL: http://svn.apache.org/viewvc?rev=1798657&view=rev
Log:
SLING-981 document support for ACLs and principals in jcr content loader

Modified:
    sling/site/trunk/content/documentation/bundles/content-loading-jcr-contentloader.mdtext

Modified: sling/site/trunk/content/documentation/bundles/content-loading-jcr-contentloader.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/content-loading-jcr-contentloader.mdtext?rev=1798657&r1=1798656&r2=1798657&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/content-loading-jcr-contentloader.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/content-loading-jcr-contentloader.mdtext Wed Jun 14 07:51:34 2017
@@ -280,10 +280,10 @@ Those tests can be used as verified exam
 By adding a `security:acl` object to a content node definition in JSON you can define an ACL for this node. For each array entry in this example an ACE is added. Example:
 
     {
-      "security:acl": [
-          { "principal": "TestGroup1", "granted": ["jcr:read","jcr:write"] },
-          { "principal": "TestUser1", "granted": ["jcr:read"], "denied": ["jcr:write"] }
-      ]
+        "security:acl": [
+            { "principal": "TestGroup1", "granted": ["jcr:read","jcr:write"] },
+            { "principal": "TestUser1", "granted": ["jcr:read"], "denied": ["jcr:write"] }
+        ]
     }
 
 If ACLs already exist on the node you can add an `order` property to each array entry controlling the position where the new ACE is inserted into the list of existing ACEs. Possible values for this property: