Hi Micheal, > I would like to use Ws-Secureconversation to sign messages (I will be using > one-way SSL to encrypt)
In Secure Conversation, we create a security context ( Security Context Token ) and use the keys derived from that to sign and encrypt messages. So there are 2 steps. First we send a request to the web service to the web service with some claims and establish a security context. Then we use that context to derive keys to secure the actual messages to consume the web service. So does this fit in to your scenario ? Are you going to expose your web service through SSL ? > I am using WSO2 WSAS and have setup a security configuration for my service > (this is a wizard that defines the service's policy) and keystore in the > WSAS management console.. but i can't figure out the next step.. In WSAS, there are pre-defined policies for Secure Conversation. In WSAS 2.2, scenarios 9 - 15 are Secure Conversation scenarios. So if you choose a secure conversation scenario and assign key stores, that's it. It is easy as that. > According to this Axis2 book that I am using, the policies need to be added > to the WSDL so that the axis2 codegen will include the policy information in > the generated code...however the book does not cover secure conversation. In secure conversation also it is the same. When you apply the policy using the security configuration, those will appear on the generated WSDL. So Axis2 code generator can make use of those policies when generating stubs for the web service. So to consume this service, all you need to do is add the RampartConfig assertion to the the Stub and call the service. Rampart will handle establishing the security context according to the given policy transparently and the client need not to worry about that. thanks, /nandana --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
