Update ca bundle to new set #30
Merged
Conversation
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
AaronAtDuo
force-pushed
the
update_ca_bundle
branch
from
f6826db to
c82502a
Compare
jeffreyparker
approved these changes
Mar 20, 2025
Contributor
jeffreyparker
left a comment
jeffreyparker
left a comment
There was a problem hiding this comment.
Verified that the new ca_certs.pem is identical to the new cert bundle
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
Replace the CA bundle with the new set
Motivation and Context
So the client keeps working after the existing certs expire
How Has This Been Tested?
Automated tests pass
Manually tested auth using the demo application
Types of Changes