[
https://issues.apache.org/jira/browse/CXF-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283805#comment-14283805
]
Sergey Beryozkin edited comment on CXF-6206 at 1/20/15 1:16 PM:
----------------------------------------------------------------
Niels, using JAX-RS API, not JAAS API, guarantees the portability of JAX-RS
services. Note I mentioned I'm open to supporting doAs on the RS chain too but
I think it is becoming off-topic for this JIRA - can you please open a new
improvement JIRA issue ? By the way I did not get what you implied with regard
to JSR250. I have tests where a JAAS filter is used with RolesAllowed, etc
was (Author: sergey_beryozkin):
Niels, using JAX-RS API, not JAAS API, guarantees the portability of JAX-RS
services. Note I mentioned I'm open to supporting doAs on the RS chain too but
I think it is becoming off-topic for this JIRA - can you please open a new
improvement JIRA issue ? By the way I did not get what you impled with regard
to JSR250. I have tests where a JAAS filter is used with RolesAllowed, etc
> 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)
