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.

Hi, is the types for the default translations from the recipes in supertokens-auth-react exported?

When I access the application in firefox, I get an error "Please provide a valid domain name" in the frontendConfig section.

Hi please here me here how to setup the supertokens. I am using nest I have 2 microservice: M1 and M2 as API gateway. I have setup the supertokens in M1. it takes cred from M2 and signIn. and return Jwt tokens. In M2(no st) when i verify this token in M2 it gives : { "message": "Invalid token", "error": "Unauthorized", "statusCode": 401 }

I'm adding additional formFields to my front end (custom UI on flutter) -- how do I access them on my python backend? This page (https://supertokens.com/docs/thirdpartyemailpassword/custom-ui/email-password-login) says: On the backend, the formFields array will be available to you for consumption. -- but where?

I have a question regarding the Apple login process. It seems that sometimes the app doesn't prompt me to share my email address. Most of the time, it doesn't ask, but occasionally, it does. What determines this behavior, and how can we control it? Thank you for your assistance.

Is there an easy way to bypass passwordless authentication for security scans? We were looking to use zap just in our development environment for security testing but wasnt sure on the best way for it to bypass auth. We were thinking we might just have to create another login page thats username/password for the zap user.

Ok I am using this example, to access the user role using the jwtpayload, https://supertokens.com/docs/emailpassword/common-customizations/sessions/user-information-front-end. But I run into the error jwtpayload.role is not part of the properties

hello, wondering if supertokens supports the oauth flow? I have an app we'd like to migrate but we have everything setup for oauth. Including token validation via Jwks.

Trying to view the dashboard on localhost, but getting a 404 error on login. I've already created a user following instructions here: https://supertokens.com/docs/thirdparty/pre-built-ui/setup/dashboard.