Disable CA Pinning: Add constructor parameter#56
Merged
cisco-annikiti merged 2 commits intoJul 16, 2026
Merged
Conversation
cisco-annikiti
marked this pull request as ready for review
July 14, 2026 18:17
jeffreyparker
approved these changes
Jul 16, 2026
cisco-annikiti
deleted the
ZTCAPIN-496-disable-ca-pinning-add-constructor-parameter-duo-api-nodejs
branch
July 16, 2026 13:36
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.
Description
Add enableCAPinning constructor parameter to the Duo API client that allows disabling CA pinning. When disabled, the TLS library validates connections using Node.js's default CA bundle instead of the pinned certificates. TLS verification remains enforced in all cases.
Motivation and Context
Part of the CA Pinning Standardization initiative. Provides a configuration option to disable CA pinning for scenarios where customers cannot upgrade and need an immediate workaround during certificate changes.
How Has This Been Tested?
Added 3 unit tests covering:
All tests pass (npm test).
Types of Changes