feat(api): Implement refresh token strategy #235
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.
Remember to add the following code in
shared/config/.env
and.env.test
This pull request introduces several significant changes to the authentication module, including the addition of refresh token functionality, scheduled token cleanup, and various dependency updates.
Authentication Enhancements:
Refresh Token Implementation:
refreshToken
method toAuthenticationController
to handle refresh token requests.refreshAuthTokens
method inAuthenticationService
to refresh authentication tokens.refreshAuthTokens
andcreateAuthTokenPair
methods inJwtManager
for token management. [1] [2]Token Cleanup Service:
TokenCleanupService
to periodically clean up expired refresh tokens using a cron job.TokenCleanupService
inAuthenticationModule
.Dependency and Configuration Updates:
Dependencies:
@nestjs/schedule
anduuid
toapi/package.json
. [1] [2]Configuration:
ApiConfigService
to includeIssuedRefreshToken
entity in the database configuration.JwtConfigHandler
.Utility and Testing:
Utility Functions:
TimeUtils
for parsing duration strings to seconds.Testing:
auth/refresh-token.spec.ts
.