This is an automated email from the ASF dual-hosted git repository.
enorman pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git
The following commit(s) were added to refs/heads/master by this push:
new 30d551c fix rendering problems in the Managing permissions
(jackrabbit.accessmanager) page
30d551c is described below
commit 30d551cd913bd35752e72e910b2c5a82d7e07c4c
Author: Eric Norman <[email protected]>
AuthorDate: Sun Oct 11 15:16:16 2020 -0700
fix rendering problems in the Managing permissions
(jackrabbit.accessmanager) page
---
...anaging-permissions-jackrabbit-accessmanager.md | 78 ++++++++++++----------
1 file changed, 44 insertions(+), 34 deletions(-)
diff --git
a/src/main/jbake/content/documentation/bundles/managing-permissions-jackrabbit-accessmanager.md
b/src/main/jbake/content/documentation/bundles/managing-permissions-jackrabbit-accessmanager.md
index 4710280..836b825 100644
---
a/src/main/jbake/content/documentation/bundles/managing-permissions-jackrabbit-accessmanager.md
+++
b/src/main/jbake/content/documentation/bundles/managing-permissions-jackrabbit-accessmanager.md
@@ -10,49 +10,52 @@ The `jackrabbit-accessmanager` bundle delivers a REST
interface to manipulate us
## Privileges
-| Name | Description |
-|--|--|
-| jcr:read | the privilege to retrieve a node and get its properties and their
values |
-| jcr:readAccessControl | the privilege to get the access control policy of a
node |
-| jcr:modifyProperties | the privilege to create, modify and remove the
properties of a node |
-| jcr:addChildNodes | the privilege to create child nodes of a node |
-| jcr:removeChildNodes | the privilege to remove child nodes of a node |
-| jcr:removeNode | the privilege to remove a node |
-| jcr:write | an aggregate privilege that contains: jcr:modifyProperties
jcr:addChildNodes jcr:removeNode jcr:removeChildNodes |
-| jcr:modifyAccessControl | the privilege to modify the access control
policies of a node |
-| jcr:lockManagement | the privilege to lock and unlock a node |
-| jcr:versionManagement | the privilege to perform versioning operations on a
node |
-| jcr:nodeTypeManagement | the privilege to add and remove mixin node types
and change the primary node type of a node |
-| jcr:retentionManagement | the privilege to perform retention management
operations on a node |
-| jcr:lifecycleManagement | the privilege to perform lifecycle operations on a
node |
-| jcr:all | an aggregate privilege that contains all predefined privileges |
+Name | Description
+--- | ---
+jcr:read | the privilege to retrieve a node and get its properties and their
values
+jcr:readAccessControl | the privilege to get the access control policy of a
node
+jcr:modifyProperties | the privilege to create, modify and remove the
properties of a node
+jcr:addChildNodes | the privilege to create child nodes of a node
+jcr:removeChildNodes | the privilege to remove child nodes of a node
+jcr:removeNode | the privilege to remove a node
+jcr:write | an aggregate privilege that contains: jcr:modifyProperties
jcr:addChildNodes jcr:removeNode jcr:removeChildNodes
+jcr:modifyAccessControl | the privilege to modify the access control policies
of a node
+jcr:lockManagement | the privilege to lock and unlock a node
+jcr:versionManagement | the privilege to perform versioning operations on a
node
+jcr:nodeTypeManagement | the privilege to add and remove mixin node types and
change the primary node type of a node
+jcr:retentionManagement | the privilege to perform retention management
operations on a node
+jcr:lifecycleManagement | the privilege to perform lifecycle operations on a
node
+jcr:all | an aggregate privilege that contains all predefined privileges
## Add or modify permissions
To modify the permissions for a node POST a request to
`/<path-to-the-node>.modifyAce.<html or json>`. The following parameters are
available:
-| Name | Description |
-|--|--|
-| principalId | The id of the user or group to modify the access rights for |
-| order | The position of the entry within the list (see below for details) |
-| privilege@[privilege_name] | One param for each privilege to modify. The
value must be either 'granted', 'denied' or 'none'. |
-| restriction@[restriction_name] | (since 3.0.4) One param for each
restriction value. The same parameter name may be used again for multi-value
restrictions. The value is the target value of the restriction. |
-| restriction@[restriction_name]@Delete | (since 3.0.4) One param for each
restriction to delete. The parameter value is ignored and can be anything. |
+Name | Description
+--- | ---
+principalId | The id of the user or group to modify the access rights for
+order | The position of the entry within the list (see below for details)
+privilege@[privilege_name] | One param for each privilege to modify. The
value must be either 'granted', 'denied' or 'none'.
+restriction@[restriction_name] | (since 3.0.4) One param for each restriction
value. The same parameter name may be used again for multi-value restrictions.
The value is the target value of the restriction.
+restriction@[restriction_name]@Delete | (since 3.0.4) One param for each
restriction to delete. The parameter value is ignored and can be anything.
The `order` parameter may have the following values:
-| Value | Description |
-|--|--|
-| `first` | Place the target entry as the first amongst its siblings |
-| `last` | Place the target entry as the last amongst its siblings |
-| `before *xyz*` | Place the target entry immediately before the sibling whose
name is *xyz* |
-| `after *xyz*` | Place the target entry immediately after the sibling whose
name is *xyz* |
-| numeric | Place the target entry at the indicated numeric place amongst its
siblings where *0* is equivalent to `first` and *1* means the second place |
+ Value | Description
+--- | ---
+`first` | Place the target entry as the first amongst its siblings
+`last` | Place the target entry as the last amongst its siblings
+`before *xyz*` | Place the target entry immediately before the sibling whose
name is *xyz*
+`after *xyz*` | Place the target entry immediately after the sibling whose
name is *xyz*
+numeric | Place the target entry at the indicated numeric place amongst its
siblings where *0* is equivalent to `first` and *1* means the second place
Responses:
-| 200 | Success |
-| 500 | Failure, HTML (or JSON) explains failure. |
+
+Status Code | Description
+--- | ---
+200 | Success
+500 | Failure, HTML (or JSON) explains failure.
Example with curl:
@@ -75,10 +78,17 @@ Remove existing restriction example with curl:
To delete permissions for a node POST a request to
`/<path-to-the-node>.deleteAce.<html or json>`. The following parameters are
available:
+Parameter Name | Required | Description
+--- | --- | ---
+`:applyTo` | yes | An array of ids of the user or group whose permissions are
to be deleted.
Responses:
-| 200 | Success |
-| 500 | Failure, HTML (or JSON) explains failure. |
+
+Status Code | Description
+--- | ---
+200 | Success
+500 | Failure, HTML (or JSON) explains failure.
+
Example with curl:
curl -F:applyTo=myuser http://localhost:8080/test/node.deleteAce.html
