Updated behavior of the refresh token in the database after logout #688
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.
Description
After the logout or sign-in the token will not be deleted, status will be changed to
EXPIRED
.Summary of changes
How test the changes
POST /auth/signup
- Create new auth token withACTIVE
status.POST /auth/signin
- Update previous auth token and setEXPIRED
status. Create new auth token withACTIVE
status.POST /auth/logout
- Update all previous auth tokens withACTIVE
status and setEXPIRED
status.yarn test
Related issues
[Job Launcher] - Change the behavior of the refresh token in the database after logout#666