You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by as...@apache.org on 2016/04/20 07:09:50 UTC

svn commit: r1740049 - /sling/site/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.mdtext

Author: asanso
Date: Wed Apr 20 05:09:50 2016
New Revision: 1740049

URL: http://svn.apache.org/viewvc?rev=1740049&view=rev
Log:
SLING-5638 - Sling:alias property not working if user does not have read access to the root node

* document limitation

Modified:
    sling/site/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.mdtext

Modified: sling/site/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.mdtext?rev=1740049&r1=1740048&r2=1740049&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.mdtext (original)
+++ sling/site/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.mdtext Wed Apr 20 05:09:50 2016
@@ -19,6 +19,17 @@ When dealing with the new resource resol
 * `sling:internalRedirect` – This property when set on a node in the `/etc/map` tree (see below) causes the current path to be modified internally to continue with resource resolution.
 * `sling:alias` – The property may be set on any resource to indicate an alias name for the resource. For example the resource `/content/visitors` may have the `sling:alias` property set to `besucher` allowing the resource to be addressed in an URL as `/content/besucher`.
 
+#### Limitation of `sling:alias` for Principal with a limited access
+
+Assuming there is
+
+* An User named `testuser`
+* An ACE with deny `jcr:all` in `/` for `everyone`
+* An ACE with allow `jcr:read` in `/content` for `testuser`
+
+If the `sling:alias` property (e.g. `myalias`) is set directly in `/content`, the User `testuser` will not be able to address the resource `/content` in an URL as `/myalias`.
+Instead if the `sling:alias` property is set in any resource under `/content` (e.g. `/content/visitors`) the `sling:alias` feature will work as usual.
+
 ### Node Types
 
 To ease with the definition of redirects and aliases, the following node types are defined: