To reproduce the error do a login, make a call to a protected API Endpoint and you should get a 401 because the access token expired and was not refreshed.
If you login and wait at least 120 seconds the refresh token expires and triggers a token refresh.
Describe the bug
When the token expires, it does not trigger a refresh and does not get renewed.
Only the lifetime of the refresh token triggers a refresh.
Expected behavior:
If the lifetime of the token expires, the refresh is triggered.
If the refresh token expires, the user gets logged out automatically.
Environment
Darwin
v20.10.0
3.10.0
3.10.0
2.9.7
npm@10.8.3
-
ssr
,css
,plugins
,runtimeConfig
,modules
,build
,vite
,lodash
,auth
@pinia/nuxt@0.5.1
,nuxt-lodash@2.5.3
,@vueuse/nuxt@10.7.2
,@sidebase/nuxt-auth@0.9.4
-
nuxt-auth: V0.9.4
Reproduction
I am using Django with Dango REST framework and simple JWT as Backend.
This is my auth configuration:
To reproduce the error do a login, make a call to a protected API Endpoint and you should get a 401 because the access token expired and was not refreshed. If you login and wait at least 120 seconds the refresh token expires and triggers a token refresh.
Describe the bug
When the token expires, it does not trigger a refresh and does not get renewed. Only the lifetime of the refresh token triggers a refresh.
Expected behavior: If the lifetime of the token expires, the refresh is triggered. If the refresh token expires, the user gets logged out automatically.
Additional context
No response
Logs
No response