如何在WCF客户端中接受自签名SSL证书？-Howtoacceptaself-signedSSLcertificateinaWCFclient?

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.

您需要找到X509CertificateCollection并将证书添加到该集合。我遇到了一个在Ssl上运行的SmtpClient的问题。

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).

通过挂钩System.Net.ServicePointManager.ServerCertificateValidationCallback或实现System.Net.ICertificatePolicy并将我自己安装的证书标识为有效/可信（附加到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.

这本身不是WCF的东西，但从我所知道的，这也应该转换为WCF。这完全取决于WCF在引擎盖下的用途。

13  

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.

这是使WCF客户端接受任意证书所需的最少代码量。这不安全。仅用于测试。如果这个代码发狂并吃掉你的小猫，不要怪我。

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?

代码无耻地从最不实用的答案解除了是否可以强制WCF测试客户端接受自签名证书？