Allow direct access to modify the TLS config #2238
Open
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
For work we need direct access to the tls config to customise the
ServerCertVerifier
.Also direct access allow any further config changes to made without any changes to tonic
Solution
To solve access to the tls i have added a method to
ClientTlsConfig
calledmodify_config
(could be named somthing else maybe).this allows users to directly modify
tokio_rustls::rustls::ClientConfig
to fit their needs.this function is called in
TlsConnector::new
after all tonic config changes are set