There are times when SSL certificates are used to verify identity and to provide TLS and there are cases when only the wire encryption matters. In the later case, I sometimes need to be able handle server certificates that are not valid by SSL’s standard rules. This could be because the cert is not signed by a trusted certificate authority or is expired, etc. When I encounter this problem and am for various reasons unable to deal with the root cause, there is a simple technique that allows you to plug in your own strategy to determine certificate validity.
Basically you do the following:
- In a seam of bootstrapping code, you’ll want to add a ServerCertificateValidationCallback to the WCF ServicePointManager
Here’s a working example that accepts any SSL Certificate as valid:
ServicePointManager.ServerCertificateValidationCallback = (object sender, X509Certificate cert, X509Chain chain, SslPolicyErrors errors) => true;
With this patched strategy in place, your WCF client will now accept any SSL certificate its given. Note that, in the lambda body, you can put in your own logic to interrogate the parameters for what you consider to be acceptable:
The logic applied can be more or less rigorous than the default certificate validation strategy. The beauty of this approach is in the power of its simple implementation.