Consistent optional behavior for X.509 certificate thumbprints #12
Conversation
This file contains 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.
This package automatically calculates X.509 certificate thumbprints. This behavior was not accounted for in the existing
JWK.Validateimplementation, causing inconsistent behavior withNewJWKFromMarshalwhen the inputtedJWKMarshalJWK Set did not contain these optional parameters.This pull request changes the
JWK.Validatebehavior to ignore comparing thex5tandx5t#S256parameters when they are not present in the original.See #11 for the relevant issue.