You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2014/03/21 18:01:50 UTC

[jira] [Updated] (CXF-5632) Support collocating SAML SSO RequestAssertionConsumerService with the actual endpoint

     [ https://issues.apache.org/jira/browse/CXF-5632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Beryozkin updated CXF-5632:
----------------------------------

    Issue Type: Improvement  (was: Bug)

> Support collocating SAML SSO RequestAssertionConsumerService with the actual endpoint
> -------------------------------------------------------------------------------------
>
>                 Key: CXF-5632
>                 URL: https://issues.apache.org/jira/browse/CXF-5632
>             Project: CXF
>          Issue Type: Improvement
>          Components: JAX-RS Security
>            Reporter: Sergey Beryozkin
>            Priority: Minor
>
> We support RACS Service running as a separate endpoint which is the best approach. 
> However in some cases it may be simpler to have RACS acting as the target endpoint interceptor, sitting just in front of the SAML SP interceptors enforcing the authentication.
> RACS service establishes the security context and redirects the user to the actual endpoint. 
> RACS interceptor will set the context directly on the message and will let the SAML SP interceptors validate it



--
This message was sent by Atlassian JIRA
(v6.2#6252)