Hi Phil; Hope this[1] may be helpful.
Thanks & regards. - Prabath [1]:http://blog.facilelogin.com/2008/07/web-services-security-encryption-with.html Phil Davies wrote: > Hi, I've scoured the web for this particular problem, but no answer yet. > > > > I'm trying to build a WS client. I am using axis2-1.3, and I can > successfully query the web services without security. > > > > When I add security, I still don't get any SOAP header, only the same > outgoing request. I am adding security by (a) making sure the Rampart > module (1.3) is globally engaged, and (b) adding the module and > OutflowSecurity elements to the axis2.xml file (see below). > > > > I'm fairly sure the axis2.xml file is getting used, because if I break > the xml in (say) the OutflowSecurity element and restart Tomcat, I get a > complaint from the servlet. Apart from that there's no sign that the > OutflowSecurity element is being processed at all. > > > > Are there other factors which need to be present before rampart will add > security to the message headers? > > > > Any help appreciated. > > Thanks > > Phil Davies > > > > Added to axis2.xml: > > <module ref="rampart"/> > > > > <parameter name="OutflowSecurity"> > > <action> > > <items>UsernameToken Timestamp</items> > > <user>wsuser</user> > > > <passwordCallbackClass>com.PasswordGetter</passwordCallbackClass> > > </action> > > </parameter> > > > > > > > > > ------------------------------------------------------------------------ > > No virus found in this incoming message. > Checked by AVG. > Version: 7.5.549 / Virus Database: 270.9.0/1777 - Release Date: 11/9/2008 > 9:53 AM --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
