[
https://issues.apache.org/jira/browse/CXF-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283733#comment-14283733
]
Sergey Beryozkin commented on CXF-6206:
---------------------------------------
JAASAutheniticationFilter is a standard JAX-RS 2.0 ContainerRequestFilter and
hence it is not going to be removed. Not sure what you mean by the standard
interceptors.
JAASAutheniticationFilter and doAs just does not work due to some JAX-RS
runtime implementation restrictions, but to be honest, IMHO I do not see it as
a major issue. I'm open though to updating the filter to actually getting
working woith doAs.
I do not think JAASLoginInterceptor need to become any more complex than it
already is.
> 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)
