fix: require certverifier in client context#92
Merged
Conversation
richard-ramos
requested review from
gmelodie and
vladopajic
and removed request for
a team
June 17, 2026 20:24
vladopajic
approved these changes
Jun 17, 2026
gmelodie
approved these changes
Jun 18, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Require client-side
TLSConfigvalues to include a certificate verifier before creating aClientContext.Without this guard, a client config with no verifier could reach SSL context setup without installing certificate verification. The new check fails fast with an explicit error instead of allowing that state.