[fix] handle token refresh after logout #15
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
After a logout, making a token refresh attempt without this change means the execution reach the auth service. That one will attempt to verify whether the RT from the headers and the RT hash in the DB match. But the RT hash from the DB was deleted on logout => 500 error
|
ERROR [ExceptionsHandler] Cannot read properties of undefined (reading 'sub') |
|
add
in the video you will see he is calling the guard by is tag
|
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.
After a logout, making a token refresh attempt without this change would make the execution reach the auth service. That one will attempt to verify whether the RT from the headers and the RT hash in the DB match. But the RT hash from the DB was deleted on logout => 500 error