10

This may be a stupid question but I just can't find the answer.

What I would like to do: I have a WCF service hosted by IIS. It is working perfectly, I can access the wsdl, I have a self-signed certificate for the server etc. I would like to call this service from a WPF client.

The problem is, since I have a self-signed certificate, I get the following exception when calling the service: Could not establish trust relationship for the SSL/TLS secure channel with authority 'localhost'.

If I access the site (or the service) from a browser, it is no problem, because the browser warns me about the certificate, and gives me the choice of viewing the page anyway. But the WPF client just throws an exception.

I don't want to completely turn off the authentication process, I simply would like to give the users the option of ignoring this warning (as browsers do).

Can anyone provide some code for this? If you ran into a good, detailed tutorial about this, it would be awesome too. (See, my problem with the tutorials I've found is the lack of details)

Tenshiko
  • 1,450
  • 3
  • 17
  • 33
  • I changed the question to reflect the problem with self-signed certificates not belonging to the default trusted root certificates. – John Leidegren Feb 12 '11 at 09:37

2 Answers2

21

Here's the minimum amount of code you need to make WCF client accept an arbitrary certificate. This is not secure. Use for testing only. Don't blame me if this code goes berserk and eats your little kitten.

ServicePointManager.ServerCertificateValidationCallback +=
            new System.Net.Security.RemoteCertificateValidationCallback(EasyCertCheck);

The call back:

bool EasyCertCheck(object sender, X509Certificate cert,
        X509Chain chain, System.Net.Security.SslPolicyErrors error)
{
    return true;
}

Code shamelessly lifted from the least helpful answer to Is it possible to force the WCF test client to accept a self-signed certificate?

Community
  • 1
  • 1
user8032
  • 1,221
  • 1
  • 9
  • 17
6

You can register the certificate yourself. If load the certificate in the client as well, and then register the it as trusted you shouldn't get that warning.

You need to find a X509CertificateCollection and add the certificate to that collection. I had this kind of problem with a SmtpClient running over Ssl.

By hooking the System.Net.ServicePointManager.ServerCertificateValidationCallback or implementing System.Net.ICertificatePolicy and identify my own installed certificate as valid/trusted (attached to the System.Net.ServicePointManager.CertificatePolicy).

This is not WCF stuff per se, but from what I could tell, this should translate to WCF as well. It all depends what WCF is uses under the hood.

John Leidegren
  • 59,920
  • 20
  • 131
  • 152
  • 1
    Could you please specify where to write this stuff? What class should implement the interface etc? I'm absolutely new to this side of WCF, I've never used secure connections or IIS, so I'm still a bit lost... – Tenshiko Feb 12 '11 at 10:09
  • If you hook `System.Net.ServicePointManager.ServerCertificateValidationCallback` do you get a request to validate the certificate? – John Leidegren Feb 13 '11 at 22:00
  • 1
    A non-code approach to this would be to trust the certificate on your dev machine and test environment. As explained here http://stackoverflow.com/a/11296429/178620 – Doguhan Uluca Feb 01 '13 at 17:36