-
Notifications
You must be signed in to change notification settings - Fork 275
Support setting optional JWT headers #126
Comments
I initially didn't implement it as it wasn't required. On Tue, Nov 22, 2016, 6:23 AM Erik Kristensen notifications@github.com
|
Would be nice to support all the other headers that are acceptable in a JWS which is used by JWT https://tools.ietf.org/html/draft-ietf-jose-json-web-signature-41#page-11 |
I should have PR for this by the end of the week.
…On Tue, Nov 29, 2016, 12:05 PM Erik Kristensen ***@***.***> wrote:
Would be nice to support all the other headers that are acceptable in a
JWS which is used by JWT
https://tools.ietf.org/html/draft-ietf-jose-json-web-signature-41#page-11
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#126 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AE_mfcxbtZp4yqeKxuYJvAmVuV9OBTtZks5rC6SVgaJpZM4K4xa0>
.
|
Ping on this? |
See RFC -- https://tools.ietf.org/html/draft-ietf-oauth-json-web-token-32#section-5
While the
typ
header is optional it is good practice when creating JWT tokens to settyp
toJWT
(see https://tools.ietf.org/html/draft-ietf-oauth-json-web-token-32#section-3.1)The text was updated successfully, but these errors were encountered: