You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
System.Net.Security TLS resumption and client-certificate tests fail together on Windows #131992
The first two failures show that connections resumed after changing the client certificate, when resumption was expected to be disabled. The third unexpectedly received a client certificate when none should have been sent.
Because all failures occurred in the same Windows work item and involve retained TLS session/client-certificate state, they may share an underlying SChannel session-cache or resumption issue.
This is potentially related to #58927, but the observed assertions and failure behavior are different.
Note
This issue was drafted with GitHub Copilot.
Known issue validation
Build: 🔎https://dev.azure.com/dnceng-public/public/_build/results?buildId=1542869 Error message validated:[System\.Net\.Security\.Tests\.(SslStreamTlsResumeTests\.ClientChangeCert_NoResume|SslStreamNetworkStreamTest\.SslStream_NegotiateClientCertificateAsyncTls13_Succeeds)] Result validation: ✅ Known issue matched with the provided build. Validation performed at: 8/7/2026 11:29:53 AM UTC
Activity
dotnet-policy-service commentedon Aug 7, 2026
Tagging subscribers to this area: @dotnet/ncl, @bartonjs, @vcsjones
See info in area-owners.md if you want to be subscribed.
Fix SslStream client certificate credential caching (#132079)