SslStream.IsMutuallyAuthenticated calls are expensive on Windows

[rzikm]

On Windows, client SslStream instances need to check if the client certificate was used via native API to SSPI. This call seems to be quite expensive if user calls the property getter often (e.g. for audit logging ber HTTP/2 request).

We should consider doing some internal caching since the value of the property should not change during the lifetime of the SslStream instance, with an exception of post-handshake client certificate negotiation.

[ghost]

Tagging subscribers to this area: @dotnet/ncl, @bartonjs, @vcsjones
See info in area-owners.md if you want to be subscribed.

Issue Details

---

On Windows, client SslStream instances need to check if the client certificate was used via native API to SSPI. This call seems to be quite expensive if user calls the property getter often (e.g. for audit logging ber HTTP/2 request).

We should consider doing some internal caching since the value of the property should not change during the lifetime of the SslStream instance, with an exception of post-handshake client certificate negotiation.

Author:	rzikm
Assignees:	-
Labels:	area-System.Net.Security, untriaged
Milestone:	-

[ghost]

Tagging subscribers to this area: @dotnet/ncl, @bartonjs, @vcsjones
See info in area-owners.md if you want to be subscribed.

Issue Details

---

On Windows, client SslStream instances need to check if the client certificate was used via native API to SSPI. This call seems to be quite expensive if user calls the property getter often (e.g. for audit logging ber HTTP/2 request).

We should consider doing some internal caching since the value of the property should not change during the lifetime of the SslStream instance, with an exception of post-handshake client certificate negotiation.

Author:	rzikm
Assignees:	-
Labels:	area-System.Net.Security, os-windows, tenet-performance
Milestone:	-