[jira] Resolved: (SLING-599) Add support for authentication/authorization methods in servlet request API

["Felix Meschberger (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger resolved SLING-599.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: Engine 2.0.4

Committed slightly modified patch in Rev. 682946 and deployed SNAPSHOT version 2.0.3-incubator-20080805.210203-4.

The modification concerns the import of the useradmin package which I marked as resolution:=optional and moving the inner class to the end of the class file.

Please close this issue, if this is ok for you. Thanks.

> 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
>            Assignee: Felix Meschberger
>            Priority: Minor
>             Fix For: Engine 2.0.4
>
>         Attachments: SlingHttpServletRequestImpl.java-2.patch, 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.