Hi, Thanks for your email. My WSDL is not java based and does not have the security header information. I have the keystore details to connect to my webservice. I am able to consume the webservice through SOAP UI by configuring the SSL info or the keystore details.
However I am using axis2's WSDL2java to create the client and rampart for the security header. I am not able to form the correct policy.xml . Find the SOAP request for which I have manipulated the security header manually through SOAP UI. This is the request I need to form through the rampart API. Please help me if you have any suggestions or ideas. Thanks, Natanasabai. <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:test="http://www.walgreens.com/test/";> <soapenv:Header> <wsse:Security xmlns:wsse=" http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd "> <wsse:BinarySecurityToken xmlns:wsu=" http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd " wsu:Id="Id-0001332817793287-fa74d0d44f712f8103100000-2" ValueType=" http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3 " EncodingType=" http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary "> MIIDFjCCAtQCBE+RlnwwCwYHKoZIzjgEAwUAMHExCzAJBgNVBAYTAlVTMREwDwYDVQQIEwhJbGxpbm9pczESMBAGA1UEBxMJRGVlcmZpZWxkMRIwEAYDVQQKEwlXYWxncmVlbnMxDjAMBgNVBAsTBUVDb21tMRcwFQYDVQQDEw5TYW5kZWVwIE1ha2tlcjAeFw0xMjA0MjAxNzAxNDhaFw0yMDA3MDcxNzAxNDhaMHExCzAJBgNVBAYTAlVTMREwDwYDVQQIEwhJbGxpbm9pczESMBAGA1UEBxMJRGVlcmZpZWxkMRIwEAYDVQQKEwlXYWxncmVlbnMxDjAMBgNVBAsTBUVDb21tMRcwFQYDVQQDEw5TYW5kZWVwIE1ha2tlcjCCAbcwggEsBgcqhkjOOAQBMIIBHwKBgQD9f1OBHXUSKVLfSpwu7OTn9hG3UjzvRADDHj+AtlEmaUVdQCJR+1k9jVj6v8X1ujD2y5tVbNeBO4AdNG/yZmC3a5lQpaSfn+gEexAiwk+7qdf+t8Yb+DtX58aophUPBPuD9tPFHsMCNVQTWhaRMvZ1864rYdcq7/IiAxmd0UgBxwIVAJdgUI8VIwvMspK5gqLrhAvwWBz1AoGBAPfhoIXWmz3ey7yrXDa4V7l5lK+7+jrqgvlXTAs9B4JnUVlXjrrUWU/mcQcQgYC0SRZxI+hMKBYTt88JMozIpuE8FnqLVHyNKOCjrh4rs6Z1kW6jfwv6ITVi8ftiegEkO8yk8b6oUZCJqIPf4VrlnwaSi2ZegHtVJWQBTDv+z0kqA4GEAAKBgG3X+p6aKblD9zxH9zb32+sey0AKxEm6/0ogFXNTUip9a7U0HtYpMuuJu64iYPI37gVy2tKZ8uD67Mrc0r+LlwqucOHI5lkUtljJKOqMBDBvpG7y/J0vl5EdubpSOq5KDbUycdVaw+PqEFNe69QI0Nt9SZYAtX3WLWnC3FG8q9LKMAsGByqGSM44BAMFAAMvADAsAhRZIocw5gcX4nMdP8+7XskBQBboGAIUWgOwoV89xZSzVjfhj8NG8VlqoCY= </wsse:BinarySecurityToken> </wsse:Security> </soapenv:Header> <soapenv:Body> <test:TestRequest> <name>Curious George</name> </test:TestRequest> </soapenv:Body> </soapenv:Envelope> Natanasabai C| Architect | Walgreens Ecommerce | VNET: From USA 973-368-9700 x463524 | Cell:+91-9790014978 On Wed, Apr 25, 2012 at 7:56 PM, Philippe A. <futhar...@gmail.com> wrote: > I am not doing that myself but I would expect common scenarios should work > fine. What matters are the features used by the server and features > supported by the client. The client is only concerned with the wsdl. > > 2012/4/24 Natanasabai C <nad...@gmail.com> > >> Hi, >> >> I would like to know if I can use rampart 1.6.0 along with axis2 1.6.0 in >> the client side to invoke any other secured web services which is been >> exposed by some other technology. >> Please clarify. >> >> Appreciate your help. >> >> Thanks, >> Natanasabai. >> >> > > > -- > Philippe > >
