To actually include the SAML Token in the security header, you need to also have either a SecurityPolicy that references a SamlToken policy, or else set up WSS4J using the older "Action" based approach. For an example of the policy case, please take a look at the SAML test data here:
http://svn.apache.org/viewvc/cxf/trunk/systests/ws-security-examples/src/test/resources/org/apache/cxf/systest/wssec/examples/saml/ Colm. On Mon, Jun 3, 2013 at 11:25 AM, patch_78 <[email protected]> wrote: > Hi, > > I would like to implement custom SAML callback handler that inserts SAML2 > assertion into SOAP header. But my custom SAML callback handler class is > not > invoked. Here is my applicationContext.xml > > <jaxws:client id="HelloServiceClient" > serviceName="svc:GreeterService" > xmlns:svc="http://apache.org/hello_world_soap_http"; > serviceClass="org.apache.hello_world_soap_http.Greeter" > address="http://localhost:10080/service/GreeterService"; > wsdlLocation="WEB-INF/wsdl/hello_world.wsdl"> > <jaxws:properties> > <entry key="ws-security.saml-callback-handler" > value="com.example.SamlCallbackHandler" /> > > </jaxws:properties> > </jaxws:client> > > Any suggestions? > > Thanks, > patch > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/ws-security-saml-callback-handler-not-invoked-tp5728636.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
