Hi. Is there any way to change expiration time of tokens depending on the way session created? Now user gets its session using

auth/signinup/code

, then sends otp (we use passwordless recipe)

auth/signinup/code/consume

which gives them tokens. This works fine, but now we want users of mobile app, which we are developing have tokens which will expire after a day, not after several hours as now. TIA.

Is there a way to route directly to the sign up or sign in form? Right now, i have a "Sign Up" and "Sign in" button and they both load the "Sign Up" form

add user without sign up ?

How do the

supertokens-node

verifySession

and

Session.getSession

functions behave in case the session is expired? Do they check this? or will they return `null`/`undefined` in such an scenario?

Hi, I have a problem with signing up into my self-hosted backend. I was following instructions in https://supertokens.com/docs/emailpassword/quick-setup/backend. I am using Angular application, and I'm trying to integrate SuperTokens into my app. My backend is in the same project as the main app, could this be a problem? Thanks for help in advance!

need help about flask API

Colleagues, I need some advice. Can I use Google OAuth Access Token to authorize my server? How do I validate them?

Has anyone found that when they're logged in with super tokens and the backend is verifying their ID, that after they move off the frontend tab for a bit and come back, the userId is rendered as null on the backend? But then when the frontend is refreshed, the userId is correctly set again

Hi Supertokens Team, I hope this message finds you well. I am currently working on integrating Supertokens into my application, which consists of Vue.js on the frontend and Nest.js on the backend. Initially, I successfully implemented the Supertokens login functionality using the SaaS version, and everything worked smoothly. To facilitate local development, I decided to switch to the Docker version of Supertokens by setting up a local instance and updating the connectionUrl accordingly. After successfully completing the setup, including table creation, both the Supertokens core and database containers appear to be running correctly on my local environment. However, upon switching the backend's connectionUri to the local URL, I encountered an issue. The login form displays as expected, and I can successfully log in with Google authentication. However, instead of being redirected to the application's homepage, the Supertokens session refresh logs continuously appear, causing an infinite loop. When I revert the connectionUri to the SaaS version, everything functions correctly. I've attached a portion of the logs generated endlessly on the frontend for your reference. Could you please provide guidance on what might be causing this issue? Any insights or suggestions would be greatly appreciated.

hey @rp_st , i am getting error while creating a session,