Forum Discussion

jtslimited's avatar
jtslimited
New Contributor
4 years ago

The signature or decryption was invalid

Hi All! When I issue a request using SoapUI 3.5 I get a successful response. When I attempt the same request using SoapUI 5.6, I get a failure response, <faultcode>wsse:FailedCheck</faultcode> <faul...
  • jtslimited's avatar
    jtslimited
    4 years ago

    Okay. I have a bead on the issue. I was reviewing with a colleague today that observed through Fiddler that the content-length was not consistent with the request body length. the difference in content-length reflected the number of lines in the message. On a whim, we used Notepad++ to convert all newline characters to end of line characters and voila! Success!!! Somewhere between Fiddler and our text editor, the end of line characters were being converted to newline characters. 

jtslimited's avatar
jtslimited
New Contributor

Hey Rich! Thanks for the suggestion. I'm having trouble with SoapUI 5.6 trusting Fiddler as a proxy. So I pivoted to a simple .net application that posts the request I've copied out of SoapUI 3.5. The Fiddler traces for raw request body between SoapUI 3.5 and my utility are a match. I'll continue to investigate. 

jtslimited's avatar
jtslimited
New Contributor
4 years ago

Okay. I have a bead on the issue. I was reviewing with a colleague today that observed through Fiddler that the content-length was not consistent with the request body length. the difference in content-length reflected the number of lines in the message. On a whim, we used Notepad++ to convert all newline characters to end of line characters and voila! Success!!! Somewhere between Fiddler and our text editor, the end of line characters were being converted to newline characters.