[SLING-9689] Handle authentication requirements for children of protected resources when internal mappings

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Authentication, ResourceResolver
• Assignee: Unassigned
• Reporter: Robert Munteanu
• Created: 25/Aug/20 08:55
• Updated: 25/Aug/20 08:55

Description

The following class of scenarios will not have authentication requirements correctly generated:

/content
    +-- parent
        +-- child
            +-- sling:vanityPath = "/vanity"

where /content/parent is a protected resource. See https://sling.apache.org/documentation/the-sling-engine/mappings-for-resource-resolution.html#interactions-between-mappings-and-authentication-requirements-1 and SLING-9622 for a longer discussion.

Issue Links

• relates to: SLING-9622 Avoid registration of auth requirements for aliases and vanity paths