-
Notifications
You must be signed in to change notification settings - Fork 291
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
Anticipate RefreshToken #138
Comments
I think that is not possible right now, but seems like a use case for #132 even though that approach has its own drawbacks as described in the PR. Is that what you meant? |
Hi jonathansamines. Yes! It's the use case! |
@fcioffi as you can see, we are not implement the buffer functionality. However the readme was updated to reflect the use-case it's drawbacks and a possible solution. Hope that helps! |
Hi @jonathansamines, thanks for your info. But I don't understand how do you suggest to resolve the issue? Where the README was updated? I understand that you would like to resolve the issue not at library level but an optional parameter on function token.expired() for a subtraction? Thanks, |
Hi @fcioffi the readme was updated at Access token section. The reason why we are not willing to resolve this at the library, is because of the drawbacks described at #132, being the main reason the arbitrariety of the time that could be used as buffer expiration value. |
Is possibile to anticipate the token expiration so when I call token.expired() it returns true some minutes before expiration?
Thanks,
Francesco
The text was updated successfully, but these errors were encountered: