You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2010/08/11 15:34:16 UTC
[jira] Created: (SLING-1641) HTTP Authenticator does not behave
correctly
HTTP Authenticator does not behave correctly
--------------------------------------------
Key: SLING-1641
URL: https://issues.apache.org/jira/browse/SLING-1641
Project: Sling
Issue Type: Bug
Components: Commons
Affects Versions: Commons Auth 1.0.0
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: Commons Auth 1.0.0
The HTTP Authenticator included with the Commons Auth bundle currently does not behave well with respect to logging out and requesting credentials:
(1) sling:authRequestLogin parameter
The sling:authRequestLogin parameter should be supported with both values BASIC (for new mechanism) and 1 for backwards compatibility. Setting the parameter should always cause a 401 response from the authentication handler
(2) sendUnauthorized
The method should not do anything (except logging) if called on a committed response
(3) dropCredentials
The dropCredentials method should always send a 401 response if the Authorization header is set in the response and the response has not been committed yet.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1641) HTTP Authenticator does not behave
correctly
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated SLING-1641:
-------------------------------------
Component/s: Authentication
(was: Commons)
> HTTP Authenticator does not behave correctly
> --------------------------------------------
>
> Key: SLING-1641
> URL: https://issues.apache.org/jira/browse/SLING-1641
> Project: Sling
> Issue Type: Bug
> Components: Authentication
> Affects Versions: Auth Core 1.0.0
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: Auth Core 1.0.0
>
>
> The HTTP Authenticator included with the Commons Auth bundle currently does not behave well with respect to logging out and requesting credentials:
> (1) sling:authRequestLogin parameter
> The sling:authRequestLogin parameter should be supported with both values BASIC (for new mechanism) and 1 for backwards compatibility. Setting the parameter should always cause a 401 response from the authentication handler
> (2) sendUnauthorized
> The method should not do anything (except logging) if called on a committed response
> (3) dropCredentials
> The dropCredentials method should always send a 401 response if the Authorization header is set in the response and the response has not been committed yet.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1641) HTTP Authenticator does not behave
correctly
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed SLING-1641.
------------------------------------
Close after release
> HTTP Authenticator does not behave correctly
> --------------------------------------------
>
> Key: SLING-1641
> URL: https://issues.apache.org/jira/browse/SLING-1641
> Project: Sling
> Issue Type: Bug
> Components: Authentication
> Affects Versions: Auth Core 1.0.0
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: Auth Core 1.0.0
>
>
> The HTTP Authenticator included with the Commons Auth bundle currently does not behave well with respect to logging out and requesting credentials:
> (1) sling:authRequestLogin parameter
> The sling:authRequestLogin parameter should be supported with both values BASIC (for new mechanism) and 1 for backwards compatibility. Setting the parameter should always cause a 401 response from the authentication handler
> (2) sendUnauthorized
> The method should not do anything (except logging) if called on a committed response
> (3) dropCredentials
> The dropCredentials method should always send a 401 response if the Authorization header is set in the response and the response has not been committed yet.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1641) HTTP Authenticator does not behave
correctly
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved SLING-1641.
--------------------------------------
Resolution: Fixed
Fixed in Rev. 984402
> HTTP Authenticator does not behave correctly
> --------------------------------------------
>
> Key: SLING-1641
> URL: https://issues.apache.org/jira/browse/SLING-1641
> Project: Sling
> Issue Type: Bug
> Components: Commons
> Affects Versions: Commons Auth 1.0.0
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: Commons Auth 1.0.0
>
>
> The HTTP Authenticator included with the Commons Auth bundle currently does not behave well with respect to logging out and requesting credentials:
> (1) sling:authRequestLogin parameter
> The sling:authRequestLogin parameter should be supported with both values BASIC (for new mechanism) and 1 for backwards compatibility. Setting the parameter should always cause a 401 response from the authentication handler
> (2) sendUnauthorized
> The method should not do anything (except logging) if called on a committed response
> (3) dropCredentials
> The dropCredentials method should always send a 401 response if the Authorization header is set in the response and the response has not been committed yet.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.