Contributions
Re: The signature or decryption was invalid
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 charactersto 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.4.5KViews1like0CommentsRe: The signature or decryption was invalid
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.4.4KViews0likes1CommentThe 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> <faultstring>The signature or decryption was invalid</faultstring> <detail>error:04091068:rsa routines:INT_RSA_VERIFY:bad signature</detail>. Furthermore, if I copy the message payload from 5.6 back to 3.5, I get a successful response. Does anyone have any working knowledge as to why this may be? Thanks in advance!Solved4.4KViews0likes3Comments