[
https://issues.apache.org/jira/browse/SLING-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620017#action_12620017
]
Christopher Elkins commented on SLING-599:
------------------------------------------
Ah, yes, I see that now. My code uses getUserPrincipal(), so I must've suffered
from some tunnel vision.
An updated patch is forthcoming.
> Add support for authentication/authorization methods in servlet request API
> ---------------------------------------------------------------------------
>
> Key: SLING-599
> URL: https://issues.apache.org/jira/browse/SLING-599
> Project: Sling
> Issue Type: Improvement
> Components: Engine
> Reporter: Christopher Elkins
> Priority: Minor
> Attachments: SlingHttpServletRequestImpl.java.patch
>
>
> Although SlingAuthenticator does populate some authentication state in the
> request, it does so in an non-portable way (from a Servlet API perspective).
> For example, it sets the remote user identifier as a request attribute
> whereas one familiar with the Servlet API would expect to obtain it by
> calling getRemoteUser().
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
