feat: allow configurable expiration for refreshToken #220
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.
This pull request introduces a major change to the refresh token handling in the
@labdigital/federated-tokenpackage. The main improvement is the addition of support for a configurableexpiresInoption when setting refresh tokens, allowing for custom expiration times or session-based expiration. This change is thoroughly tested with new and updated unit tests.Refresh Token Expiration Improvements:
refreshToken.expiresInoption to thesetRefreshTokenmethod, enabling custom expiration times or session-based expiration for refresh tokens (cookies-base.ts).cookies-base.test.tsto verify behavior with default, custom, and session expiration settings for refresh tokens. [1] [2]Documentation and Release Notes:
@labdigital/federated-tokenpackage.