[release/7.0] fix TLS resume with client certificates on Linux #81795
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
partial backport of #79898
fixes #79869
Customer Impact
because of the TLS resume, customer can see unexpected dependencies and incorrect behavior when using client certificates on Linux. The TLS cache in in process memory so the impact is limited.
Testing
New tests were added to cover the scenarios.
The tests depend on
IsMutuallyAuthenticated
property that may be incorrect because of #65563.Since we do not port fix for that I made tests Linux specific for the release branch. (there is no resume on macOS)
(the tests added in main also discover gaps so the product change #79898 had more fixes for Window)
Regression
yes, new in 7.0
Risk Low
We did not do TLS resume at all prior 7.0 on Linux. This change brings back the behavior in one more case we missed.