Add exp
claim to generated JWTs
#8
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes it so that JWTs are created with an
exp
claim of 5 minutes into the future. JWTs are only used to obtain the session, and should be short-lived.On https://embedding-demo.metabase.com/, the iframe gets generated with a token like the following (truncated):
This decodes to:
The
expiresIn
claim has no meaning to Metabase or to the JWT spec. Because there is noexp
claim in this token, Metabase will consider it as never expiring, and it can be re-used forever to obtain a new session until the JWT secret is rotated.