Cap node-auth JWT certificate chains - #5060
Open
Sinck wants to merge 1 commit into
Open
Conversation
10 tasks
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.
Follow up on review feedback from the self-signed node-auth JWT work by bounding the certificate chain carried in each token. The bound stops untrusted requests from triggering unbounded certificate processing, keeps local minters and API validation compatible, and makes an oversized local bundle diagnosable without noisy logs.
Related issues
None.
Type of Change
Breaking Changes
Testing
Additional Notes
Follow-up to #4718.