You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can't say it's a bug or it's volountary but this, I think, a strange behaviour.
The refresh token API endpoint is called at the same time as session refresh.
A first attempt of session refresh is done right after the signIn process. The returned access_token and refresh_token are rightly set to auth state and cookies but the next refresh tentative is still using the previous refresh_token...
Am I missing something or an issue really occurs ?
Is refreshing tokens in same time as session refresh a normal behaviour ?
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered:
After some debugging, I realized that the access_token and refresh_token stored in the app state are the old one, and those in the cookie are the valid one. But the tokens that are used during the refresh are those of the app state, right?
Is is intentional or something needs to be done on my side (or package side ?)
Environment
Darwin
v20.17.0
3.14.1592
3.15.0
2.10.4
[email protected]
-
default
@nuxt/[email protected]
,@sidebase/[email protected]
,@nuxt/[email protected]
,@nuxtjs/[email protected]
,[email protected]
,@vueuse/[email protected]
,@nuxtjs/[email protected]
,@nuxt/[email protected]
,@pinia/[email protected]
,[email protected]
,[email protected]
,@nuxtjs/[email protected]
-
Reproduction
Set your nuxt.config.ts auth options :
signIn to your app
Describe the bug
I can't say it's a bug or it's volountary but this, I think, a strange behaviour.
The refresh token API endpoint is called at the same time as session refresh.
A first attempt of session refresh is done right after the signIn process. The returned access_token and refresh_token are rightly set to auth state and cookies but the next refresh tentative is still using the previous refresh_token...
Am I missing something or an issue really occurs ?
Is refreshing tokens in same time as session refresh a normal behaviour ?
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: