Hello.

There is:

  • WCF service on NET 4.5.2 with standard basic authentication by transferring login and password.
  • SSL certificate is used to ensure data encryption between the client and the server.
  • service is deployed on IIS.

Problem:

The problem lies in the fact that the client does not want to work with this service (generated by Visual Studio tools) written in NET 2.0 (use is mandatory). An exception is thrown: " SoapHeaderException: Error checking message security ."

By experimenting, it turned out that if on the server side you disable authentication (that is, if the service does NOT request a login and password) and try to contact the service there will be no problems - everything works with a bang. Problems arise only when authentication is enabled.

Something intelligible how to solve this problem and get the client to work did not find it. Your thoughts, gentlemen? )

PS When authentication is enabled with this service, the client written on NET 3.0 works fine.

  • 2
    SOAP - mammoth excrement, now in REST fashion. .NET 2.0 - mammoth excrement, Microsoft support for which ended 4 years ago. Standardization, cross-platform and other advantages of SOAP - fiction and dust in the eyes. This is the general picture. And now to the details. Support for .NET 3.5 SP1 is rotten recently, at the time of release .NET 4.5 was supported, so from this point you can count on at least something. Well, if you want .NET 2.0 - shaman, for example ( stackoverflow.com/q/11263640 is an example of shamanism). - Athari

0