Support separate TLS handshake certificate/private key in Client #440
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
### Motivation Support separate TLS handshake certificate/private key parameters independent from auth, enabling proper mTLS handshake configuration. ### Modifications - Add and to . - Wire to C client via and . - Update end-to-end test to provide client cert/key for TLS endpoints. ### Verifying this change - Ran only for cases; TLS endpoints pass with client cert/key. ### Documentation - [x] doc-not-needed (Type hints updated in ).
BewareMyPower
approved these changes
Nov 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Motivation
Support separate TLS handshake certificate and private key parameters independent from auth, enabling proper mTLS handshake configuration on the client.
Modifications
Verifying this change
Documentation