Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Speculations about future JWT extensions #24

Closed
selfissued opened this issue Sep 16, 2022 · 0 comments · Fixed by #33
Closed

Speculations about future JWT extensions #24

selfissued opened this issue Sep 16, 2022 · 0 comments · Fixed by #33

Comments

@selfissued
Copy link
Collaborator

A note in the spec says:

Implementers are warned that JWTs are not capable of encoding multiple subjects and are thus not capable of encoding a verifiable credential with more than one subject. JWTs might support multiple subjects in the future and implementers are advised to refer to the JSON Web Token Claim Registry for multi-subject JWT claim names or the Nested JSON Web Token specification.

Speculating about how other specs might or might be extended seems unhelpful and inappropriate. Also, the "not capable" statement is overly strong, as JWTs could be extended to do so. I suggest replacing the note above with:

At the time of this writing, JWTs do not have a representation for multiple subjects and are thus not capable of encoding a verifiable credential with more than one subject. Should the working group decide to do so, we could create a new JWT claim for this purpose and register it in the JSON Web Token Claims Registry.

Attn: @OR13

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant