Does WCF support WS-Security with SOAP 1.1?

In order to use WS-Addressing ( wsHttpBinding ), but with SOAP 1.1 (SOAP 1.2 being the default), you need to define a custom WCF binding (e.g. In config) and use that.

In order to use WS-Addressing (wsHttpBinding), but with SOAP 1.1 (SOAP 1.2 being the default), you need to define a custom WCF binding (e.g. In config) and use that: and then in your endpoint definition, use: Of course, you can extend the custom binding defined above with additional properties, e.g. Or others. For more very detailed, very useful info on WCF bindings and how to "compose" your own custom bindings in config, read this excellent MSDN article Service Station: WCF Bindings In Depth by Aaron Skonnard.

You must either use BasicHttpBinding which also supports TransportWithMessageCredentials (SOAP 1.1 + HTTPS + WS-Security X.509 Certificate Token profile) or create custom binding based on all your needs.

I've tried changing the wsHttpBinding to basicHttpBinding, but it causes an exception and doesn't make it to the 3rd party server. From what I've read, basicHttpBinding is incompatible with certificate authenticate. Am I wrong?

– Stefan Moser Mar 23 at 23:02 MSDN says that certificate authentication is supported: msdn.microsoft. Com/en-us/library/… – Ladislav Mrnka Mar 23 at 23:33.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.