The Nonce value of the UsernameToken is not correctly managed:
- you send a SOAP request with WSS header (containing a Username with PasswordDigest, including a Nonce value) from SoapUI.
- You just put the WSS header the SOAP enveloppe of your request (you not use a WSS configuration).
SoapUI will generate a WSS header each time you send the request, and Nonce value will be different at each call.
- you get a correct reply after the first call.
- you resend the same request (second call) and you get the same reply as previous instead of an error because we use the same Nonce values.
Bug
New
Major