-
Notifications
You must be signed in to change notification settings - Fork 1.3k
issue new refresh token every call to refresh access token #712
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @barneag, thanks for reaching out! Have you seen I believe it would not be best practice to simply extend the existing refresh token's lifetime (though again you can set a long lifetime if needed). See gh-297 for an example, which summarizes best practices for SPAs and the use of refresh tokens. Do you have any additional thoughts on this? |
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed. |
@barneag just wanted to make sure you saw my above comment? |
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue. |
Hey @sjohnr |
Today Refresh token has a fixed time of expiration by default.
It would be nice to create mechanism for new expiration for refresh token,
every time we refresh access token.
thanks!
The text was updated successfully, but these errors were encountered: