Canonical JWT encoding #6
Open
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.
From perl v5.18, the key order of hash is randomized and two JSON encoded strings may be different even if they come from same structure of hash.
Encoding to JWT has same problem.
This simple sample code says
Encoding results are completely deferent even if they have same claims.
JWT spec doesn't refer to above things but I think the same JWT claims should have exactly same JWT string.
This pull-req is intended to fix that problem by using canonical JSON encoding.