[
https://issues.apache.org/jira/browse/CXF-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14284932#comment-14284932
]
Niels Bertram commented on CXF-6206:
------------------------------------
True the above will run but not under control of the JVM security manager,
hence making your system susceptible to session fixation attacks. If you follow
the call actions of {{Subject.doAs()}} you will see that this call ends in
{{java.security.AccessController.doPrivileged}} which is a native method and
causes your subsequent flows being executed in a new thread (disclaimer
ASFAIK). Is it stands right now, {{JAASAuthenticationFilter}} does work if one
does not care about security, but if one does then this filter is a big no go
as it is hard wired to prevent secure execution.
> 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)
