[SLING-5638] Sling:alias property not working if user does not have read access to the root node

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Resource Resolver 1.4.12
• Component/s: ResourceResolver
• Assignee: Antonio Sanso
• Reporter: Antonio Sanso
• Created: 05/Apr/16 13:01
• Updated: 25/Apr/16 08:34
• Resolved: 20/Apr/16 05:10

Description

issue ;- Sling:alias property not working if user is having read only access to /content folder.

Steps :-

1) Login using admin/admin.
2) Create page say mypage.html and provide sling:alias property say mypagealias.
3) Create test user and provide read only access on /content folder from useradmin console.
4) log out from admin user.
5) Hit the page http://localhost:4502/content/<path_of_page>/mypage.html it will ask for the login ( login as test user ) it opens the page
6) hit the alias page http://localhost:4502/content/<path_of_page>/mypagealias.html - it wont work.

sling:alias property get stored at jcr:content node for the page in /content, so user with read access on /content should access it. please correct me in case I am missing something.

to make it work user has to give root( read only ) access to test user only then test user can access alias page.