Hey there, i'm implemanting a creation of user profil on my own database while a user is signin up. The user is created after the originalImplementation of my signup, and use some additional fields. My issue is, if there is an error in my database interaction, the user is still created in supertokens, and I can't do it before the supertokens signup because i need the user id. Is there a way to revert the user creation if is there any error ?

hello, @rp_st , I have multiple frontends, and they are entirely different base domains, how can I make supertokens work? I already used header based auth. The point is multiple frontend uses the same project, means same supertokens config.

Hi. In my nestjs app, i have implemented the auth guard. After a successfull login, at the next reuqest, my

response.headersSent

is true and the user get redirected to login. So I guess that the verifySession is failed but i dont have info why it was failed even though the original login was successfull. the err is not set:

await verifySession()(request, response, (res) => {
      err = res;
    });

how can I debug and understand why am i getting redirected to login page? Thanks

Hello, we're using Supertokens python sdk in an AWS Lambda + FastAPI and it's working great, but now we'd like to use some supertokens functions outside of the API, like getting user id by email, or managing roles directly from other backend processes. I've noticed it's possible if the init function is called beforehand, how would you refactor the documentation lambda code example so Supertokens can be used outside of FastAPI implementation ? Is there anything else to consider for such usage ?

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 team , Supertokens involve third party cookies for auth in case of cookie based authentication . Chrome has disabled thirdparty cookies for 1% users and soon will be disabling third party cookies . How will the cookie based auth work then ? Would we need to move to header based in that case ? If yes , how will session sharing work ?

Hello, I have been having trouble with getting Next.JS App Directory SSR to work properly. I've been following the documentation on https://supertokens.com/docs/thirdparty/nextjs/app-directory/protecting-route#sessions-with-server-components--pre and looked at the repository (https://github.com/supertokens/next.js/tree/canary/examples/with-supertokens/app). (I last checked these pages and followed them today, 2/9/2024) The components sessionAuthForNextJS.tsx and tryRefreshClientComponent.tsx are the same and I followed the code stated in home.tsx. Looking at my configuration files, they seem to be correct. When I attempt to log in, it works just fine and such. Then if I try to go to my dashboard, which has the SSR authentication requirement, I will first be redirected to the auth page for a moment then pushed to the home page '/'. Then every other attempt of trying to go to the dashboard will just continue to redirect me to the home page '/'. If convert the SSR pages into their client side version then it works just fine, however I want to use SSR for increased performance and user experience. I then got confused with the middleware, thinking it was part of the SSR before realizing it was only for APIs, but the middleware approach did fix my issues, until expiration occurred and I'd get a "Authentication required" message. As a temporary fix to this, the user would need to go back to the home page and then they'd be able to go to the dashboard and its sub pages. This sort of works but there are pages where users would go straight to a sub page within the dashboard, so they'd get this message often. Figuring out that the middleware was only for APIs, I went back and commented it out. I am now at square one with SSR authentication again and can't seem to figure out why I am only redirected to the home page and never allowed into my dashboard.

Hey, I am using golang fiber with some nextjs and reactjs frontend. i am having issue with CORS https://codefile.io/f/7ToerynrFw any help will be apprciated 🙂

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

Hi, I'm trying to setup the dashboard. I'm trying to create a user using the CLI command but I'm getting

{"status":"INVALID_EMAIL_ERROR"}

curl --location --request POST 'https://xxx.aws.supertokens.io/recipe/dashboard/user' \
--header 'rid: dashboard' \
--header 'api-key: <YOUR-API-KEY>' \
--header 'Content-Type: application/json' \
--data-raw '{"email": "<YOUR_EMAIL>","password": "<YOUR_PASSWORD>"}'

My email ends in

.dev

is there some validation going on?