Hey, we recently changed the domain our app is hosted on and we've started to a get a bunch of fairly mysterious 403s?

Hello folks, We are building an open-source platform (http://github.com/agenta-ai/agenta) where we want to include features for authentication. Each of our users hosts our platform in their own instances. We were thinking of using supertokens for authentication. One idea we had is to have one central supertokens core instance hosted by us that is shared by all users of our platform (meaning each user hosts their own instance of agenta, and their agenta backend calls supertokens core hosted by us). This would allow us to measure the real number of our users. Now, the challenge is that means that the supertokens core that we host will be openly available to all the internet without API keys. The question is: what security risks does this present? I understood that the supertokens core provides an endpoint for session creation. However, the backend itself is the one that verifies this session internally. So, if my understanding is correct, even if some attacker used supertokens core to create a session, they won't be able to user this session token in a users backend. Is this correct?

Is it a bug, when the user metadata in the dashboard is empty, but it is in the db. Or just not implemented yet because of beta

hi, is it expected that using Supertokens with next.js disables static optimization entirely? Our entire app is protected, so we get this error in the Vercel logs:

Warning: You have opted-out of Automatic Static Optimization due to `getInitialProps` in `pages/_app`. This does not opt-out pages with `getStaticProps`

This causes some strange downstream issues for us, because now everything in our client needs to get rendered via serverless functions

Is there a way to manually generate a verification link for a user? Found https://supertokens.com/docs/emailpassword/common-customizations/email-verification/generate-link-manually but not yet documented. The use case for this being the username has been changed, which marks it as not verified anymore, I want to then generate a new verification link and send that through to the new username once it has changed. Is this possible currently? or would I only be able to fire the new verification email once the user has created a session with the new username? thanks in advance 🙂

Hello, I (akshat-g-07 on github) have been wanting to contribute to this community (supertokens-auth-react) and I was trying to setup the project in my local. I went through the steps mentioned in the Contributing.md. And I think something didn't go as expected that's why I am not able to setup. If someone can connect with me (so that I can share my screen) for few minutes to help me there, it would be really helpful. We can discuss it here as well if connecting is not convenient. Thanks in advance 🙂

I am getting this 500 internal server error - custom ui, nestjs backend

Is is possible for Frontend(Next js) to get the user meta data ?

Is it possible to give custom userId to supertokens.? I know supertokens uses uuid. I was taking a look at the override functions. Wondering if I can pregenerate the user_id that will be used in supertokens table

When I try to use the use functions in the frontend (Angular)

ts
// login function
  async login(email: string, password: string) {
    console.log(
      await ThirdPartyEmailPassword.emailPasswordSignUp({
        formFields: [
          {
            id: 'email',
            value: email,
          },
          {
            id: 'password',
            value: password,
          },
        ],
      })
    );
  }

I get 404 error, stating that the route in the backend (NestJS) does not exist

POST http://localhost:3333/api/signup 404 (Not Found)

. What am I supposed to do, in order for the backend to to the correct think on those routes?