cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CXF-6206) JAASLoginInterceptor: Return proper unauthorized response when JAAS login with basic auth fails
Date Tue, 20 Jan 2015 16:34:35 GMT

    [ https://issues.apache.org/jira/browse/CXF-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283979#comment-14283979
] 

Sergey Beryozkin edited comment on CXF-6206 at 1/20/15 4:34 PM:
----------------------------------------------------------------

Christian, you stated yourself the interceptor should not deal with converting the exception
into a response, why start introducing this kind of configuration if a user can implicitly
'configure' it as suggested at

https://issues.apache.org/jira/browse/CXF-6206?focusedCommentId=14283699&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14283699

? 


was (Author: sergey_beryozkin):
Christian, you stated yourself the interceptor should not deal with converting the exception
into a response, why start introducing this kind of configuration if a user can implicitly
'configure' it as suggested at
https://issues.apache.org/jira/browse/CXF-6206?focusedCommentId=14283733&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14283733
? 

> JAASLoginInterceptor: Return proper unauthorized response when JAAS login with basic
auth fails
> -----------------------------------------------------------------------------------------------
>
>                 Key: CXF-6206
>                 URL: https://issues.apache.org/jira/browse/CXF-6206
>             Project: CXF
>          Issue Type: Improvement
>          Components: Core, Transports
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
>             Fix For: 3.1.0
>
>
> Currently we return a Fault with a AuthenticationException when JAAS login fails.
> The proper response would be a 401 status with a suitable WWW-Authenticate header.
> I experimented with turning the AuthenticationException into a 401 response in the http
transport. Not sure where to take auth type and realm from though. I am also not sure how
to distinguish basic auth from WSS Security UsernameToken. As in the second case 401 is probably
not correct.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message