WCF: The incoming message was signed with a token which was different fron what used to encrypt the body. This was not expected.

Question

For what ever reason, a critical third peaty webservice functions like this. I can connect, send a request, and receive valid response, but i still get the error message. This only happens on one server.

"The incoming message was signed with a token which was different fron what used to encrypt the body. This was not expected." (sic)

This only happens on one server, but it's critical that I get the data. I don't have control over the server and while I'm aware what the message means, frankly I don't care. It's their call how they configure their own servers and send back the proper information. All I want is the data.

Is there any "shut up and deal with it" security setting in WCF so I can get data properly from the server?

Answer 1

What kind of tokens are you using? Certificates? If so, this article might be useful: "How to: use different X509 Certificates for signing and encryption". In particular, look at the part that reads "To use multiple certificates on the client".

Answer 2

I had to open up a trouble ticket with Microsoft to solve this. Those guys are good and it raised up pretty high up the chain.

In the end it was something simple - the certificate on my machine was somehow corrupt. I had delete it and reinstall it then everything magically began to work.