[
https://issues.apache.org/jira/browse/SLING-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229908#comment-15229908
]
Antonio Sanso commented on SLING-5638:
--------------------------------------
The culprit is in the ResourceResolverImpl#resolveInternal
{code}
// no direct resource found, so we have to drill down into the
// resource tree to find a match
resource = getAbsoluteResourceInternal(null, "/", parameters, true);
{code}
this wrongly assumes that the session has reading privileges in "/"
> Sling:alias property not working if user is having read only access to
> /content folder.
> ---------------------------------------------------------------------------------------
>
> Key: SLING-5638
> URL: https://issues.apache.org/jira/browse/SLING-5638
> Project: Sling
> Issue Type: Bug
> Components: ResourceResolver
> Reporter: Antonio Sanso
> Assignee: Antonio Sanso
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
