then there is a 401 on page

so I am guessing then we need to handle that 401

using "onSessionExpired"

because the refresh token at that point is still valid

just that if I set the access token expiration for 15 minutes

and there is no activity for over 15 minutes

I need to either send user to login page or use the refresh token to get new access token with a page relod

"If no session exists, the API will return a 401 error to the client. "

I guess that statement means the access token?

just checked 401 response body and it was

should I handle that right after "superTokensNextWrapper"

or do you advice to rather use "onSessionExpired"

not sure if onSessionExpired is for the access token or rather the refresh token?

Oh right. So that 401 should be handled automatcally by the frontend SDK

oh ok

It should call the refresh endpoint on its own. If you are using

axios

, then make sure to add:

import Session from "supertokens-auth-react/recipe/session";
Session.addAxiosInterceptors(axios);

to all your axios instances.

oh ok

I'll change that now

if you are using fetch, then you don't need to do anything extra

yes using axios 🙂

makes sense

thanks I'll update it and let you know

if it is all working

thanks for all the help

So the axios thing will call the refresh endpoint automatically when it gets 401. After a successful refresh, it will call the original API again and it should all work.. In case the refresh fails too (cause the refresh token has expired), then your axios will return a 401 error and you should redirect the user to the login screen (which should also happen on its own cause of the auth wrapper)

brilliant, I'll also test the refresh token 401 redirect locally after the axios change to make sure auth wrapper working and setup correctly on my side. Thanks

Just realised that we did not mention the axios thing in the nextjs docs... hehe. will add that now

👍