Outgoing WSS cannot be applied to SOAP request soapUI 4.0

Hello,

I can't seem to reproduce this issue. Could you please provide some more information, or a screenshot to help us investigate ?

Thank you!

Regards,
Vladimir
SmartBear Sweden

Yep - I am having the same issue:

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

I am having the same issue, I upgraded to see if the new version suported SAML2 and now it doesn't work at all. Projects that used to work on version 3.6.1 opened in this new version doesn't work. I have example projects using sam 1 working in the old version but i need to get saml2 working. soapui really needs to get support for saml2 asap.

This appears to be fixed in 4.5. I am no longer having this issue. If you find this post, try 4.5