Re:Things to Use Instead of JSON Web Tokens
by Freak_NL on Monday May 08, 2017 @05:45AM
(#14290310)
Keeping the JWT format as-is is useful if you have signed (but not encrypted) tokens though; in a web browser you can use standard libraries to inspect the token and alter the UI based on a user's permissions (the final check is always the API's responsibility of course, but if there is no need to show the 'admin' link the client can do that).
[ Parent
| on HN ]
Re:Things to Use Instead of JSON Web Tokens
by theprotocol on Monday May 08, 2017 @05:49AM
(#14290330)
If it isn't encrypted, the only thing the client needs to know is that it's base64 encoded in order to inspect it. You'd need the secret to verify the signing and you probably shouldn't have that on the client-side!
So I still think the header is superfluous even for this use case.
edit: in fact, the client needs to know that it's base64 encoded to even read the header in the first place.
Re:Things to Use Instead of JSON Web Tokens
by vertex-four on Monday May 08, 2017 @06:06AM
(#14290398)
Symmetric signing is not, by far, the only use case for JWTs. Asymmetric signing, and encryption, are also well-specified and supported.
Re:Things to Use Instead of JSON Web Tokens
by theprotocol on Monday May 08, 2017 @06:13AM
(#14290434)
Good point! It slipped my mind.