RE: Axis2 - Rampart: Clientside Policy Configuration
Ok, great. Thanks for your reply Nandana! Regards, Nicolas From: Nandana Mihindukulasooriya [mailto:nandana@gmail.com] Sent: Wednesday, February 25, 2009 10:46 AM To: axis-user@ws.apache.org Subject: Re: Axis2 - Rampart: Clientside Policy Configuration Yes, this is correct. You can also do this programatically in the client like this. https://wso2.org/library/3415 Client side : step 6 But if you don't have any specific requirement do this programatically ( such as values are only available at runtime), I think your approach is fine. thanks, nandana On Tue, Feb 24, 2009 at 7:08 PM, Berner, Nicolas wrote: Hi everybody, I´m playing around with Axis2 (1.41) and Rampart (1.4). The Policy Configuration works fine. I attach a Policy to my Axis2-Service and generate the client from wsdl. So my client is already configured for my desired security operations. Until now I configured the clientside rampart-module (crypto-settings, user-settings) either static in the client-axis2.xml or dynamically in the Service-Sourcecode. The configuration-part of the client-axis2.xml looks like that: http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy";> http://ws.apache.org/rampart/policy";> client ClientPWCallbackHandler service JKS client.jks test Is this the right way to configure the client in a static way or is there another possibility? Maybe a better one? Thanks a lot in advance for your answers! Regards, Nicolas
Re: Axis2 - Rampart: Clientside Policy Configuration
Yes, this is correct. You can also do this programatically in the client like this. https://wso2.org/library/3415 Client side : step 6 But if you don't have any specific requirement do this programatically ( such as values are only available at runtime), I think your approach is fine. thanks, nandana On Tue, Feb 24, 2009 at 7:08 PM, Berner, Nicolas wrote: > Hi everybody, > > > > I´m playing around with Axis2 (1.41) and Rampart (1.4). The Policy > Configuration works fine. > > I attach a Policy to my Axis2-Service and generate the client from wsdl. > > So my client is already configured for my desired security operations. > Until now I configured the clientside rampart-module (crypto-settings, > user-settings) > > either static in the client-axis2.xml or dynamically in the > Service-Sourcecode. > > The configuration-part of the client-axis2.xml looks like that: > > > xmlns:wsu=*" > http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd > "* > > xmlns:wsp=*" > http://schemas.xmlsoap.org/ws/2004/09/policy"*> > > http://ws.apache.org/rampart/policy > "*> > > client > > ClientPWCallbackHandler ramp:passwordCallbackClass> > > service > > > > > >"org.apache.ws.security.components.crypto.Merlin"*> > > "org.apache.ws.security.crypto.merlin.keystore.type"*>JKS > > "org.apache.ws.security.crypto.merlin.file"*>client.*jks* > > > name=* > "org.apache.ws.security.crypto.merlin.keystore.password"*>*test* ramp:property> > > > > > > > > > > Is this the right way to configure the client in a static way or is there > another possibility? > > Maybe a better one? > > > > Thanks a lot in advance for your answers! > > > > Regards, > > Nicolas >
