Skip to content

How to understand "If the token is opaque (just a reference), the JWKS step will be skipped." #41

Answered by jensneuse
AnsonCode asked this question in Q&A
Discussion options

You must be logged in to vote

A JWT is not encrypted, only signed. That is, it contains all claims in JSON format, with a signature as the trailer. Opaque tokens on the other hand are, as the name indicates "opaque". They don't contain any information/claims. So, if you're using JWTs, it's possible to do "offline validation" via JWKS. With an opaque token, this doesn't work. So we're using the userInfo endpoint of the issuer to get their claims. This might be a bit more expensive, but we can cache the result so that you don't have to call the issuer for each token.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by AnsonCode
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants