[SLING-9623] ResourceMapperImpl.getAllMappings is incomplete for nested alias

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Resource Resolver 1.6.16
• Fix Version/s: Resource Resolver 1.7.0
• Component/s: ResourceResolver
• Assignee: Robert Munteanu
• Reporter: Angela Schreiber
• Created: 30/Jul/20 15:34
• Updated: 28/Aug/20 12:42
• Resolved: 18/Aug/20 14:38

Description

while investigating an issue involving sling:alias, i inadvertently created nested alias i.e. ended up having an alias define for the parent and a child page.

when looking at the values obtained from ResourceMapper.getAllMappings, i noticed that it only contains 1 combination. cross-checking however revealed that all combinations define valid paths that are properly resolved by sling.

Example

parent: /parent with alias name 'alias-parent'
child: /parent/child with alias name 'alias-child'
valid paths for the child are (and expected from ResourceMapper.getAllMappings):

• /parent/child
• /parent/alias-child
• /alias-parent/alias-child
• /alias-parent/child

actual values obtained from ResourceMapper.getAllMappings:

• /parent/child
• /alias-parent/alias-child

consequently, an consumer of ResourceMapper.getAllMappings will miss valid alias path mappings. with additional nesting or addition of multiple alias values (see SLING-9620), the number of missed paths will increase.

Issue Links

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