-
-
Notifications
You must be signed in to change notification settings - Fork 127
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
Redirect to login page after page reload in "refresh" provider #744
Comments
Hello, are there any updates on this? I'm experiencing the same issue. |
Hello 👋 Please provide a reproduction for this issue 🙏 How can I create a reproduction?Please use one of the following links to reproduce your issue.
Please ensure that the reproduction is as minimal as possible. This will allow us to isolate the issue as best as possible. Here are some more amazing posts about the importance of reproductions: |
Investigation by the community would be highly appreciated, as the team is currently focused on merging long-awaited PRs and preparing for 0.8 |
this issue occured to me, make sure you have both signInResponseRefreshTokenPointer & refreshRequestTokenPointer in refreshToken object: |
You can consider using this npm package |
Environment
OS: Windows 11
Browser: Chrome(the only one I work)
Reproduction
My nuxt.config.ts configuration
Describe the bug
It works well unless I reload the page. But after reloading the page at some point after successful login, it redirects to the login page. I analyzed the localstorage, sessionstorage, cookies of dev tools in the browser, but I couldn't find accessstoken saved in any of those areas. I only found refreshToken saved in the cookies. As far as I know, accessToken should be saved somewhere in the browser to put to the header with axios intercepter. As auth works fine unless reload page and it's not working after page reload, I assume it may be saved to memory. I couldn't find it in other areas as I stated.
If my guess is wrong, please let me know where I can find accessToken after login and how to fix this issue.
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: