[
https://issues.apache.org/jira/browse/SLING-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745616#comment-15745616
]
Felix Meschberger commented on SLING-6394:
------------------------------------------
Yes, that's correct because the Sling Authenticator has no clue about path
mapping done by the ResourceResolver. The Sling Authenticator just sees the raw
request URL and has to make assumptions on that. I don't think we can and
should do something about that.
The only way to probably approach this would be to register login requirements
for the vanity path(s).
> SlingAuthenticatior#getAnonymousResolver doesn't take in consideration
> vanityPath
> ---------------------------------------------------------------------------------
>
> Key: SLING-6394
> URL: https://issues.apache.org/jira/browse/SLING-6394
> Project: Sling
> Issue Type: Bug
> Components: Authentication
> Reporter: Antonio Sanso
>
> SlingAuthenticatior#getAnonymousResolver doesn't take in consideration
> vanityPath . This leads to cases where a resource called with a vanityPath
> rather then the real path is considered not existing.
> Test case to follow
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
