Page access with sling alias

Forum|Forum|9 years ago
March 22, 2016
3 replies
3152 views

Hi, I have a user who has read only access to all nodes under this path. /content/folder1/

I have a page like this. /content/folder1/folder2/mywebsite/pagegroupA/demo.html. folder1/folder2 are sling:OrderedFolder and pagegroupA, demo are both of type cq:Page. The user can access the page with /content/mywebsite/pagegroupA/demo.html.

If I add a sling:alias property testAlias to demo node, the user cannot access the page with /content/mywebsite/pagegroupA/testAlias.html. Sling is not able to resolve this path and throws a 404. Another user with read access to the full tree starting from root can access with the sling alias name.

My question is if there is something related to permissions for sling:alias. We have to have restricted access to the conent for certain users. thanks

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by smacdonald2008

The only information set that can address this question is https://sling.apache.org/documentation/the-sling-engine/mappings-for-resource-resolution.html.

Lokesh_Shivalingaiah

New Participant

Thats right Abhishek !!

A

abhishekbAuthor

New Participant

Yes, my testing and observation is inline with the pseudo code in that documentation. So my understanding is that if Sling doesn't finds the exact path in the repo, it will start drilling down from root for a matching alias. And if the user doesn't have access to the root, it will fail at that first step and return 404.

smacdonald2008Accepted solution

New Participant

The only information set that can address this question is https://sling.apache.org/documentation/the-sling-engine/mappings-for-resource-resolution.html.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded