Add CA bundle version and CA pinning status to the user-agent string - #56
Merged
Conversation
cisco-annikiti
marked this pull request as ready for review
July 24, 2026 09:00
jeffreyparker
approved these changes
Jul 24, 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.
Description
Append ca_bundle/1.0 and ca_pinning=enabled/ca_pinning=disabled to the User-Agent string based on the current pinning state. The User-Agent header is now set globally on the axios instance rather than per-request on the token endpoint
Motivation and Context
Provides server-side visibility into which CA bundle version clients are running and whether CA pinning is active, enabling monitoring of CA pinning rollout and diagnosing certificate-related connectivity issues
How Has This Been Tested?
Types of Changes