sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SLING-966) Make internal sling authentication publicly available
Date Wed, 06 Jan 2010 08:33:54 GMT

    [ https://issues.apache.org/jira/browse/SLING-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797030#action_12797030
] 

Felix Meschberger commented on SLING-966:
-----------------------------------------

Deployed SNAPSHOT version 0.9.0-20100106.083211-1 of the Commons Auth bundle.

> Make internal sling authentication publicly available
> -----------------------------------------------------
>
>                 Key: SLING-966
>                 URL: https://issues.apache.org/jira/browse/SLING-966
>             Project: Sling
>          Issue Type: Improvement
>          Components: Commons
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: Commons Auth 1.0.0
>
>         Attachments: SLING-966.patch, SLING-966b.patch, SLING-966c.patch
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message