Hi, I'm now developing a web app (

app.brahbrah.com

) and a centralized authentication app (

auth.brahbrah.com

) with Next.js + tRPC + SuperTokens. The centralized authentication app provides the auth web UI and auth APIs like https://supertokens.com/docs/thirdpartyemailpassword/nextjs/app-directory/setting-up-backend. The web app contains configuration files like https://supertokens.com/docs/thirdpartyemailpassword/nextjs/app-directory/init. The backend of the web app employs SuperTokens's Nodejs SDK with tRPCS. The frontend of the web app employs SuperTokens's React SDK. Previously, the old web app (

app.brahbrah.com

) contains whole authentication features with SuperTokens, there is no centralized authentication app (

auth.brahbrah.com

), and the old web app works well without any issues. After splitting the old web app (

app.brahbrah.com

) into the current web app (

app.brahbrah.com

) and a centralized authentication app (

auth.brahbrah.com

), we face a new issue that an access token will be invalid after a certain period of time. Can we achieve the above modularization? How can I fix the invalidation issue? I will paste some logs on the thread.