-
Notifications
You must be signed in to change notification settings - Fork 402
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
add support for refresh token #4
Comments
Fixed in There's some additional things we're tracking here: #7 |
Let me know if we can close this issue. |
That was fast!! I'll have a look after work. |
Brilliant + fast = brilliant. |
Just tried 0.2.0, perfect! I can see the token in the JTW session. You can close. @b2times4: you might want to file an issue in the repo you linked. I'll mention you if I find myself figuring out a working example of token refresh. |
We now have a full example available that shows how to get a valid access token (and if expired, automatically get a new one using a refresh token): I'm going to go ahead and close this issue now. |
First of all, thanks for this great library, the struggle was so real before I came across your nextjs example!
As requested in sandrinodimattia/nextjs-auth0-example#2 :
A good feature for the next release would be to store refresh token, in order to allow getting new access tokens when needed.
The text was updated successfully, but these errors were encountered: