c# - 无法为 SSL/TLS 安全通道建立信任关系

问题描述

我知道 StackOverflow 和其他资源上有很多关于此错误的信息，但它在我的开发机器上运行良好，现在在客户环境 Windows Server 2012 上运行。这是我的代码。

public sealed class Certificates
{
    private static bool subscribed = false;

    private static Certificates instance = null;

    private static readonly object padlock = new object();

    private Certificates() { }

    public static Certificates Instance
    {
        get
        {
            lock (padlock)
            {
                if (instance == null)
                    instance = new Certificates();
                return instance;
            }
        }
    }

    public void GetCertificatesAutomatically()
    {
        if (!subscribed)
        {
            ServicePointManager.ServerCertificateValidationCallback +=
                RemoteCertificateValidationCallback;
            //new RemoteCertificateValidationCallback((sender, certificate, chain, policyErrors) => { return true; });
            ServicePointManager.Expect100Continue = true;
            ServicePointManager.SecurityProtocol = SecurityProtocolType.Ssl3 |
                                                   SecurityProtocolType.Tls |
                                                   SecurityProtocolType.Tls11 |
                                                   SecurityProtocolType.Tls12;
            ServicePointManager.MaxServicePointIdleTime = 0;
            subscribed = true;
        }
    }

    private static bool RemoteCertificateValidationCallback(object sender, X509Certificate certificate, X509Chain chain, SslPolicyErrors sslPolicyErrors)
    {
        // Return true if the server certificate is ok
        if (sslPolicyErrors == SslPolicyErrors.None)
            return true;

        bool acceptCertificate = true;
        StringBuilder msg = new StringBuilder("The server could not be validate for the following reason():");

        // The server did not present a certificate
        if ((sslPolicyErrors & SslPolicyErrors.RemoteCertificateNotAvailable) == SslPolicyErrors.RemoteCertificateNotAvailable)
        {
            msg.AppendLine("    - The server did not present a certificate.");
            acceptCertificate = false;
        }
        else
        {
            // The certificate does not math the server name
            if ((sslPolicyErrors & SslPolicyErrors.RemoteCertificateNameMismatch) == SslPolicyErrors.RemoteCertificateNameMismatch)
            {
                msg.AppendLine("    - The certificate name does not match the authenticated name.");
                acceptCertificate = false;
            }

            // There is som other problem with certificate
            if ((sslPolicyErrors & SslPolicyErrors.RemoteCertificateChainErrors) == SslPolicyErrors.RemoteCertificateChainErrors)
            {
                foreach (X509ChainStatus item in chain.ChainStatus)
                {
                    if (item.Status != X509ChainStatusFlags.RevocationStatusUnknown &&
                        item.Status != X509ChainStatusFlags.OfflineRevocation)
                    {
                        SLICLog.Error($"    - {item.StatusInformation}.");
                        break;
                    }
                    if (item.Status != X509ChainStatusFlags.NoError)
                    {
                        msg.AppendLine($"    - {item.StatusInformation}.");
                        acceptCertificate = false;
                    }
                }
            }
        }

        // if validation failed, write log
        if (!acceptCertificate)
        {
            acceptCertificate = true;
        }

        return acceptCertificate;
    }
}

然后我使用了下一个代码

 Host = new Uri(credential.Domain);

 if (Host.Scheme.Contains("https"))
     Certificates.Instance.GetCertificatesAutomatically();
using (HttpWebResponse httpWebResponse = httpRequest.GetResponse() as HttpWebResponse)
            using (var response = httpWebResponse.GetResponseStream())
            using (var sr = new StreamReader(response))
            {
                token = JsonConvert.DeserializeObject<SessionInternal>(sr.ReadToEnd());
                if (token != null)
                {
                    Authorized = true;
                    token.Exprired = DateTime.Now.AddSeconds(Convert.ToDouble(token.expires_in));
                }
            }

问题是 ServerCertificateValidationCallback 在环境机器上被忽略（我从我添加的日志中知道它只是为了调试）。

在一个网站上，我读到微软不允许忽略服务器机器上的自签名证书，但不确定。相同的代码适用于 Windows10，不适用于 Windows Server 2012，API 服务器的设置也相同，我的意思是主机 url 和凭据是相同的。.NET 框架 4.7.2

更新：

我不知道为什么，但是另一个具有自签名证书的服务器可以工作，我的意思是我在环境服务器上运行代码以与另一个 API 服务器（它是另一种 API）一起工作，并且调用了 ServerCertificateValidationCallback 委托。我试图通过 Wireshark 研究网络，这是客户端/服务器之间连接不良的一部分这是与另一台服务器的正常连接，我很困惑，但代码相同，只有 API 服务器的 IP 不同，行为不同

标签： c#windows-serviceswindows-server-2012-r2

c# - 无法为 SSL/TLS 安全通道建立信任关系 - Windows Server 2012 R2

问题描述

解决方案

推荐阅读