[
https://issues.apache.org/jira/browse/CXF-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh resolved CXF-3243.
--------------------------------------
Resolution: Fixed
This issue can be marked as resolved. A SAMLCallbackHandler instance can be
configured via "ws-security.saml-callback-handler". See the system test here
for an example:
http://svn.apache.org/viewvc/cxf/trunk/systests/ws-security/src/test/java/org/apache/cxf/systest/ws/saml/SamlTokenTest.java?view=markup
Colm.
> 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
