Implemented refresh token system: refresh endpoint, logout, cookies, short lived JWT #38
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Key Changes:
Reduced JWT access token validity to around 15 minutes.
Added a new RefreshToken entity with fields: token, user, expiryDate.
Updated AuthService.login and handleGoogleOAuth methods to generate and store refresh tokens.
Refresh token is returned in a secure httpOnly cookie.
Added new API endpoint /api/auth/refresh to validate the refresh token and issue a new access token.
Added logout endpoint that deletes/inactivates the stored refresh token.
Improved overall authentication configuration to support token renewal pattern.