feat: remove session, emit SIGNED_OUT when JWT session_id is invalid
#905
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hf
force-pushed
the
hf/sign-out-session-missing
branch
from
50493b0
to
21e52ec
Compare
hf
force-pushed
the
hf/sign-out-session-missing
branch
from
21e52ec
to
6bbcf92
Compare
2 tasks
J0
approved these changes
May 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When the access token (JWT) contains a
session_idproperty which does not correspond to a row in thesessionstable, it means that the user has been signed out or the session has been destroyed in some way. Auth will send back asession_not_founderror code which can be detected by the client library and removing of the stored session with emitting theSIGNED_OUTevent should take place.