Outgoing WSS cannot be applied to SOAP request soapUI 4.0
Hello, In the new version I can't seem to apply outgoing wss to my soap requests. I don't have this issue in 3.6.1. My company cannot upgrade until this is fixed. - Steve
Forum Discussion
Sorry for the late reply. Here are a few more details. I've upgraded from 3.6.1 to 4.0. When I apply an existing
Outgoing WSS the only thing added to the request is
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"/>
Under WS-Security Configurations --> Outgoing WS-Security configurations --> Signature
Keystore test.jks
Alias test
Password xxxxxxxx
Key Identifier Type: Binary Security Token
Signature Alg <default>
Signature Canonicalization <default>
Digest Alg <default>
Use Single Cert Checked
Under WS-Security Configurations --> Keystores/Certs
Source C:\development\test.jks
Status OK
Password xxxxxxxx
This exact configuration works in 3.6.1
Outgoing WSS the only thing added to the request is
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"/>
Under WS-Security Configurations --> Outgoing WS-Security configurations --> Signature
Keystore test.jks
Alias test
Password xxxxxxxx
Key Identifier Type: Binary Security Token
Signature Alg <default>
Signature Canonicalization <default>
Digest Alg <default>
Use Single Cert Checked
Under WS-Security Configurations --> Keystores/Certs
Source C:\development\test.jks
Status OK
Password xxxxxxxx
This exact configuration works in 3.6.1