Add constructor parameter to disable CA pinning - #27
Merged
Conversation
cisco-annikiti
marked this pull request as ready for review
July 16, 2026 13:31
jeffreyparker
approved these changes
Jul 20, 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
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.
Description
Add $enable_ca_pinning constructor parameter to allow disabling CA pinning. When disabled, the TLS library validates connections using the OS trust store instead of the pinned CA bundle. TLS verification (SSL_VERIFY_PEER and verify_hostname) is always enforced regardless of this setting.
Motivation and Context
Provides a configuration option to disable CA pinning for customers who cannot upgrade during a CA bundle transition.
How Has This Been Tested?
Added unit tests covering:
Types of Changes