quic: enable client certificate authentication support #40017
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.
Description
This PR implements TLS client authentication (mTLS) support for QUIC connections, addressing the open TODO comment we have in
QuicServerTransportSocketConfigFactory::createTransportSocketFactory()
.We have modified the existing test to expect successful creation of transport socket factory with client authentication enabled and added new test cases to verify that the client certificate configuration is properly accepted and parsed.
This change aligns with RFC 9001 Section 4.4, which explicitly allows client authentication during the TLS handshake for QUIC connections.
Commit Message: quic: enable client certificate authentication support
Additional Description: Removed the TODOs and added support for TLS client authentication for QUIC.
Risk Level: Low
Testing: Unit tests and integration tests added
Docs Changes: Added
Release Notes: Added