R3 examples: switch from ES256 to EdDSA#19
Open
rohanharikr wants to merge 1 commit into
Open
Conversation
Brings the R3 examples in line with the rest of the spec, which RECOMMENDS EdDSA throughout (see protocol doc §5.2.2, §6.6.1, §7.1.4 — all token examples use EdDSA). The two R3 example headers were the only remaining ES256 references in the spec.
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.
Brings the R3 example JWT headers in line with the rest of the spec, which RECOMMENDS EdDSA throughout — protocol doc §5.2.2, §6.6.1, §7.1.4 all show EdDSA in their token examples. The two R3 header examples were the only remaining
ES256references in the spec.Diff
Two-line change in
draft-hardt-aauth-r3.md:resource+jwtexample header:"alg": "ES256"→"alg": "EdDSA"auth+jwtexample header:"alg": "ES256"→"alg": "EdDSA"No normative changes — examples only.