This is an automated email from the ASF dual-hosted git repository.
rombert 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 867d888 SLING-9622 - Avoid registration of auth requirements for
aliases and vanity paths
867d888 is described below
commit 867d888961337a8fef72a0fb65e9100708e2f927
Author: Robert Munteanu <[email protected]>
AuthorDate: Tue Aug 25 10:48:37 2020 +0200
SLING-9622 - Avoid registration of auth requirements for aliases and vanity
paths
Syntax fixes.
---
.../mappings-for-resource-resolution.md | 21 +++++++++------------
1 file changed, 9 insertions(+), 12 deletions(-)
diff --git
a/src/main/jbake/content/documentation/the-sling-engine/mappings-for-resource-resolution.md
b/src/main/jbake/content/documentation/the-sling-engine/mappings-for-resource-resolution.md
index f078bdd..2fd6ba2 100644
---
a/src/main/jbake/content/documentation/the-sling-engine/mappings-for-resource-resolution.md
+++
b/src/main/jbake/content/documentation/the-sling-engine/mappings-for-resource-resolution.md
@@ -285,23 +285,20 @@ The [Sling
authentication](/documentation/the-sling-engine/authentication.html)
Additional mappings complicate the situation, therefore additional
authentication requirements are automatically registered by Sling. For
instance, assuming the following repository structure:
-```
-/content
- +-- parent
- +-- sling:alias = "secret"
- +-- child
-```
+ /content
+ +-- parent
+ +-- sling:alias = "secret"
+ +-- child
+
and that `/content/parent` is a protected resource, authentication
requirements will automatically be registered for both `/content/parent` and
`/content/secret`.
One scenario where authentication requirements will not be registered properly
is when the child of a protected resource has an external vanity path ( or
resource mapping ) that is not a descendant of an existing authentication
requirement, such as:
-```
-/content
- +-- parent
- +-- child
- +-- sling:vanityPath = "/vanity"
-```
+ /content
+ +-- parent
+ +-- child
+ +-- sling:vanityPath = "/vanity"
In this scenario no authentication requirement will be registered for
`/vanity`, which lead to the resource being accessible without authentication.
If registering mappings for children of protected resources is desired, the
following precautions must be taken:
