Windows系统下.NET应用使用TLS1.3连接时出现Invalid token错误

问题场景 #

Windows 11系统已通过注册表启用TLS 1.3，但.NET应用使用TLS 1.3与服务器通信时触发以下SSPI相关异常，切换为TLS 1.2则正常运行：

000003E1 03:10:39.068084   8908.1      ThreadId:1, MS_Source:System.NetMessage: [7468] InitializeSecurityContext(credential = System.Net.SafeFreeCredential_SECURITY, context = 8bb628:10111, targetName = dotnet.com, inFlags = ReplayDetect, SequenceDetect, Confidentiality, AllocateMemory, InitManualCredValidation)
000003E2 03:10:39.068084   8908.1     ------------}  ExternalSourceTracer_MS rc=OK
000003E3 03:10:39.068084   8908.1     ------------{  ExternalSourceTracer_MS
000003E4 03:10:39.068084   8908.1      ThreadId:1, MS_Source:System.NetMessage: [7468] InitializeSecurityContext(In-Buffers count=2, Out-Buffer length=0, returned code=InvalidToken).
000003E5 03:10:39.068084   8908.1     ------------}  ExternalSourceTracer_MS rc=OK
000003E6 03:10:39.092392   8908.1      System.Security.Authentication.AuthenticationException: A call to SSPI failed, see inner exception. ---> System.ComponentModel.Win32Exception: The token supplied to the function is invalid
   --- End of inner exception stack trace ---
   at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
   at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest, Boolean renegotiation)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest, Boolean renegotiation)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest, Boolean renegotiation)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest, Boolean renegotiation)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest, Boolean renegotiation)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Net.Security.SslStream.AuthenticateAsClient(String targetHost, X509CertificateCollection clientCertificates, SslProtocols enabledSslProtocols, Boolean checkCertificateRevocation)

问题分析 #

该异常由SSPI调用返回InvalidToken错误导致，核心原因是TLS 1.3握手过程中客户端与服务器的协议交互不兼容，常见触发因素包括：

• .NET运行时版本对TLS 1.3的支持不足
• Windows注册表中TLS 1.3的启用配置不完整
• 服务器端TLS 1.3的加密套件或握手逻辑不符合规范

解决方案 #

1. 确认.NET运行时版本兼容性 #

• .NET Framework：仅4.8及以上版本正式支持TLS 1.3，且需搭配Windows 10 1903+或Windows 11。若版本低于4.8，升级至最新.NET Framework版本。
• .NET Core/.NET 5+：确保使用.NET 5或更高版本，此类版本原生支持TLS 1.3。

2. 验证TLS 1.3注册表配置完整性 #

检查以下注册表项的DWORD值是否正确设置（1为启用，0为禁用），修改后需重启系统：

• 客户端配置路径：HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.3\Client
  • Enabled：1
  • DisabledByDefault：0
• 服务器端配置路径（若应用作为服务端）：HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.3\Server
  • Enabled：1
  • DisabledByDefault：0

3. 临时强制使用TLS 1.2 #

若无法立即解决TLS 1.3兼容性问题，可在代码中显式指定使用TLS 1.2：

// .NET Framework 写法
System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12;

// .NET Core/.NET 5+ 写法（以SslStream为例）
var sslOptions = new SslClientAuthenticationOptions
{
    EnabledSslProtocols = System.Net.Security.SslProtocols.Tls12,
    TargetHost = "dotnet.com"
};

4. 排查服务器端TLS 1.3配置 #

确认服务器端满足以下要求：

• 支持与Windows 11兼容的TLS 1.3加密套件（如TLS_AES_256_GCM_SHA384）
• 未禁用TLS 1.3必需的握手扩展
• 服务器证书使用SHA-256及以上签名算法，符合TLS 1.3规范

内容的提问来源于stack exchange，提问作者subbaraoc