Hi, This is a show stopper for us to move our web services to QA.
We have configured synapse to perform usernametoken authentication and forward SOAP request to jboss server. This setup works fine. We are scheduled to release this within a month and suddenly we were mandated to use the SAML based security provided by our single-sign-on group. Now this is a show stopper for us to release. This means that 1. All external clients (simply clients) should first request SAML token from this single-sign-on webservice. 2. Clients should insert this SAML token into their SOAP message security header. 3. Clients send this SOAP message to our AXIS2 webservice hosted in Jboss server mediated by synapse. 4. Synapse/rampart/rahas should be reconfigured to process this SAML token (instead of usernametoken) to authenticate and allow the request to proceed. The question is how do we reconfigure synapse/rampart/rahas to process this SOAP message coming with the SAML token as the security credential. As I could not find a concrete sample or documentation of how to set up for SAML authentication, I am stuck and helpless. Could you provide me with the sample or documentation ASAP please ? Thanks, Muralidaran Chakaravarthy -- View this message in context: http://www.nabble.com/Confugring-rampart-Rahas-for-producing-and-processing-SAML-messages.-tf4670568.html#a13384580 Sent from the Synapse - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
