[
https://issues.apache.org/jira/browse/SLING-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-108.
-----------------------------------
Resolution: Fixed
Committed the implementation with Rev. 597404.
The Sling authenticator is now called by the OSGi Http Service before invoking
the main Sling servlet's service method. As a side effect, the
HttpServletRequest.getAuthType() and getRemoteUser() methods will now return
appropriate values and the Session is provided as a request attribute.
> Implement authentication in HttpContext.handleSecurity
> ------------------------------------------------------
>
> Key: SLING-108
> URL: https://issues.apache.org/jira/browse/SLING-108
> Project: Sling
> Issue Type: Improvement
> Components: Core
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> The OSGi HttpContext interface provides a method handleSecurity which is
> defined to be implemented for authenticating requests. This method is called
> before the service method of the registered and selected servlet is called.
> Sling has an implementation of this interface, the SlingHttpContext, which is
> currently also used for MIME-type mapping support. This implementation should
> do the authentication and set the request attributes accordingly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
