[SLING-966] Make internal sling authentication publicly available

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Auth Core 1.0.0
• Component/s: Authentication
• Assignee: Felix Meschberger
• Reporter: Felix Meschberger
• Created: 12/May/09 14:21
• Updated: 27/Aug/10 08:50
• Resolved: 08/Jan/10 10:39

Description

Currently the SlingAuthenticator is an internal class in the Engine bundle, which is used by the SlingMainServlet to handle the authentication as part of an OSGi HTTP Service specification HttpContext object.

To use the Sling authentication framework with the Authenticator and the AuthenticationHandlers outside of the SlingMainServlet, that is for other servlets directly registered with the OSGi HttpService the authentication functionality should be made publicly available.

One approach would be to provide a new authenticate() method in the Authenticator interface. Another option would be to provide an abstract HttpContext which already implements the HttpContext.handleSecurity method using the SlingAuthenticator instance.

Issue Links

• incorporates: SLING-1155 Add logout method to Authenticator
• incorporates: SLING-1240 Allow configuration of URL space open without credentials

Sub-Tasks

• Adapt HTTP Header Authentication Handler to new AuthenticationHandler API: Resolved
• Adapt OpenID Authentication Handler to new AuthenticationHandler API: Closed