Forum Discussion

denz97's avatar
denz97
New Contributor
11 years ago

WSS fails if request contains custom properties

I have defined a custom property which I use in my web service request.

The web service I am calling requires x509/signature token.

Before sending the request, I right-click on the request and apply an already configured "Outgoing WSS". On submit, I get an error response from the service:

<faultstring>The digitial signature in the message is invalid. Either the message was changed after it was signed or tampered with in transit.</faultstring>

If I do not use the custom property but instead use the actual value in the message, I do not get an error.

So I think the error is when SoapUI replaces the custom property with the actual value and somehow the signature is no longer valid after the web service request was changed.

Is there a way to apply the outgoing WSS only after the SoapUI has replaced all the custom properties with their corresponding values?

Thanks,

Dennis

4 Replies