Hi Vladimir,
JWT is mentioned only to say that JWTs must not use the alternative "b64":false
encoding. They must be encoded as they always have been.
JSON Web Tokens (JWTs) [JWT] MUST NOT use "b64" with a "false" value.
I don't understand why this seems to imply an alternative JWT encoding. Indeed
- the intent is the opposite - to prohibit use of the potential alternate
encoding.
Thanks,
-- Mike
-----Original Message-----
From: jose [mailto:[email protected]] On Behalf Of Vladimir Dzhuvinov
Sent: Friday, September 25, 2015 6:15 AM
To: [email protected]
Subject: [jose] JWT with JWS Unencoded Payload Options
Hi Mike,
I'm looking at the -02 draft right now, as I was considering implementing it,
at least experimentally for now.
I'm not sure I understand why JWT is mentioned in it. Is this a real use case?
Section 6 effectively implies an alternative JWT encoding, using normative
language, but this conflicts with the JWT RFC which says that "JWTs are always
represented using the JWS Compact Serialization or the JWE Compact
Serialization."
https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2ftools.ietf.org%2fhtml%2frfc7519%23section-1&data=01%7c01%7cmichael.jones%40microsoft.com%7c31e01586d3d04e874c6308d2c5ab631f%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=vAxCqdvRt%2fSaOqaYKl1bSTYtMgDQ%2fnvrPJQ1gGSk4mM%3d
Cheers,
Vladimir
On 14.09.2015 09:28, Mike Jones wrote:
> Draft -02 of the JWS Unencoded Payload Option specification makes these
> updates:
> * Added an "updates" clause for RFC 7519 because this specification
> prohibits JWTs from using "b64":false.
>
--
Vladimir Dzhuvinov :: [email protected]
_______________________________________________
jose mailing list
[email protected]
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fwww.ietf.org%2fmailman%2flistinfo%2fjose&data=01%7c01%7cmichael.jones%40microsoft.com%7c31e01586d3d04e874c6308d2c5ab631f%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=NovTPm6SUrZWlYmPnE%2f6tNPbTR%2f4kHeHBUsjP6mIsNc%3d
_______________________________________________
jose mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/jose
