News for hackers. Stuff that matters.
Re:JWT scope claim compression using a bitmap by abhishektwr on Saturday May 23, 2020 @06:29AM (#23281780)
I am curious, why will you not use OAuth 2 userinfo endpoint which can serve a lot more detail and keep claims in JWT simpler and lightweight.
Re:JWT scope claim compression using a bitmap by quaffapint on Saturday May 23, 2020 @10:47AM (#23283386)
If you can just pass around the JWT you can save a network call. I would say the size of the JWT wouldn't matter as much as that call.
Re:JWT scope claim compression using a bitmap by abhishektwr on Saturday May 23, 2020 @08:24PM (#23287935)
You still have to make network calls to obtain public key (JWKS) to validate token signature. Unless you are using shared private keys. With userinfo you will know if token is invalidated or not.

I guess it also depends on use case. If you are in domains such as banking with elevated security requirements, then probably you want to hit userinfo endpoint else you can continue with token validation with cached or stored keys.

Re:JWT scope claim compression using a bitmap by jepcommenter on Sunday May 24, 2020 @06:45AM (#23290648)
You don't pull JWKS on every request