-
Notifications
You must be signed in to change notification settings - Fork 2
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
use +jwt
SSS?
#14
Comments
Obviously, the next question is: should we register a |
Looked at the various RFC involved and yes, this does seem like the right thing to do, both eat+jwt and eat+cwt. These would replace eat-jwt and eat-cwt. Thx |
Cool, will PR this asap. |
thomas-fossati
added a commit
that referenced
this issue
Mar 9, 2023
Fix #14 Signed-off-by: Thomas Fossati <thomas.fossati@arm.com>
thomas-fossati
added a commit
that referenced
this issue
Mar 10, 2023
Fix #14 Signed-off-by: Thomas Fossati <thomas.fossati@arm.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
IANA's Structured Syntax Suffixes registry has
+jwt
, defined in RFC8417 to be "used indicate that the media type is encoded as a JWT."It looks like
application/eat+jwt
could be used instead ofapplication/eat-jwt
.The text was updated successfully, but these errors were encountered: