Add builder option to disable CA certificate pinning#108
Open
AaronAtDuo wants to merge 1 commit into
Open
Conversation
Allows callers to opt out of CA pinning while keeping TLS verification active via the OS trust store. This is a safety valve for customers who cannot upgrade when a cert chain change breaks pinning. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
1 participant
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
disableCaPinning()method toHttpandClientBuilderthat removes CA pin checks while keeping TLS verification active via the OS trust storeIllegalStateExceptionat build time if bothdisableCaPinning()anduseCustomCertificates()are set (mutually exclusive)newBuilder()pattern assetProxy()anduseCustomCertificates()Test plan
IllegalStateExceptionapi-483c5af7.test.duosecurity.comThis PR was generated with AI assistance (Claude).