Skip to content

Disable CA Pinning: Add constructor parameter#56

Merged
cisco-annikiti merged 2 commits into
masterfrom
ZTCAPIN-496-disable-ca-pinning-add-constructor-parameter-duo-api-nodejs
Jul 16, 2026
Merged

Disable CA Pinning: Add constructor parameter#56
cisco-annikiti merged 2 commits into
masterfrom
ZTCAPIN-496-disable-ca-pinning-add-constructor-parameter-duo-api-nodejs

Conversation

@cisco-annikiti

@cisco-annikiti cisco-annikiti commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

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:

  • CA pinning is enabled by default
  • CA pinning can be disabled via constructor parameter (no ca option on request)
  • TLS verification is still enforced when pinning is disabled
    All tests pass (npm test).

Types of Changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

@cisco-annikiti
cisco-annikiti marked this pull request as ready for review July 14, 2026 18:17
Comment thread lib/main.js
@cisco-annikiti
cisco-annikiti merged commit 445e8dc into master Jul 16, 2026
5 checks passed
@cisco-annikiti
cisco-annikiti deleted the ZTCAPIN-496-disable-ca-pinning-add-constructor-parameter-duo-api-nodejs branch July 16, 2026 13:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants