Hi Kasun, The issued_token sample is broken: https://issues.apache.org/jira/browse/RAMPARTC-78 Among other things, I noticed that sts-client-policy.xml is not copied into install destination.
I do not use rampart_config_set_issued_token_aquire_function() because I successfully obtain my SAML token in band (as in sts_client sample) and set it in rampart_config: rampart_config_add_saml_token (rampart_config, env, saml_token). My problem may be related to the stub code generation issues described here: http://www.nabble.com/rampart-c-not-working-with-stubs-generated-using-w sdl2c-to11731091.html I edited my stubs per their recommendation, but it did not help me. It appears that Rampart/C does not work with WSDL2C-generated stubs. Regards, StanS -----Original Message----- From: Kasun Indrasiri [mailto:[EMAIL PROTECTED] Sent: Thursday, March 06, 2008 1:32 AM To: [email protected] Subject: Re: SAML token isn't injected into the header. The issued_token example does not appear to be > working: Rampart never invoked get_issued_token() function. Hi Stan, I think the issued token sample properly worked (scenario 20 -I tested in windows) with all the other secpolicy scenarios. And regarding your problem, you have mentioned that Rampart is not invoking the get_issued_token() function. Ramprt invokes that method only if the function pointer is set as 'rampart_config_set_issued_token_aquire_function(client_config, env, get_issued_token);'. Have a look at the samples under ./samples/client/issued_token and associated secpolicies in scenario 20. Regards, Kasun.
