You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2011/03/07 13:15:59 UTC
[jira] Updated: (CXF-3243) SAML 2.0 CallBackHandler support
[ https://issues.apache.org/jira/browse/CXF-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh updated CXF-3243:
-------------------------------------
Fix Version/s: 2.4
> SAML 2.0 CallBackHandler support
> --------------------------------
>
> Key: CXF-3243
> URL: https://issues.apache.org/jira/browse/CXF-3243
> Project: CXF
> Issue Type: Improvement
> Components: WS-* Components
> Affects Versions: 2.3.1
> Environment: Windows XP, Apache Tomcat 7.0, CXF 2.3.1
> Reporter: David Morris
> Assignee: Colm O hEigeartaigh
> Fix For: 2.4
>
>
> Need a SAML2.0 CallbackHandler to be supported in WSS4J for CXF. (org.apache.cxf.ws.security.wss4j.WSS4JOutInterceptor class).
> Developed a 'hack' in org.apache.cxf.ws.security.wss4j.WSS4JOutInterceptor to call a 'custom' SAML2.0 CallbackHandler. This code works for now but would like a better implementation configurable in CXF+Spring similar to the WSPassword. I am researching for a better implementation via the CXF source code.
> Suggestion:
> Have the SAMLCallback (SAML1.0 & SAML2.0) configurable in CXF + Spring similar to the WSPasswordCallback.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira