I'm trying to create a .NET client that will consume AXIS WS.
Request should be signed (using x509 Signature) and after this usernametoken profile 1.0 should be attached.
Using SOAP-UI I can create Outgoing Security Policy with few steps described below:
1) Define keystore
2) Add WSS Signature entry and mark key identifier type as X509 Certificate or Binary Security Token
3) Add WSS Username entry
The order is important.
I cannot recreate SOAP request that would generate valid response.
I got "The signature or decryption was invalid" most of the time.
Here is valid SOAP Request from SOAP-UI:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:user="http://users.api.swd.zbp.pl"
View Complete Post