I have a FastAPI backend and a NextJS frontend. I want to use getServerSideProps to send the logged in user's data to my frontend. When I try to get the logged in user's data in getServerSideProps, I get { message: 'unauthorised' }. I think this is because the cookies in the browser are not sent to my FastAPI backend. Is this even possible?

Hi, any guide on how to use Passwordless and Session management in a plain html, js website with flask backend. Is it even possible right now?

Is the email template tied to the SMTPService class? I want to enqueue the email to an HTTP endpoint (also easier to integration test) instead of directly connecting to SMTP

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?

Meant to pop in earlier. 😅 Hope that was a fun time.

Hey, I was checking pricing page, and I've seen that you are offering MFA, but when checking docs, I see that supertokens is not MFA optimized. We have already implemented 2FA using combination of multiple recepies as suggested in docs. I'm just wondering if there is feature we are missing since we are using self hosted version without license?

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

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 just integrate supertokens in my django app (backend). I well received tokens on my frontend (simulated with Insomnia). Next step is to integrate supertokens authentication on django authentication backend. Do you have some documentation about that?

Hello ! 👋 I am evaluating Ory Kratos and Supertokens. It looks like both can fit my needs, but my main concern in with the DB high availability part. I'm planning on deploying my app on a k8s cluster and using Yugabyte for the DB, and it seems Kratos does not support it according to some old github issue they had. I'm rather unimpressed with Ory's idea of high availability, which pretty much boils down to "we have infinite horizontal scaling capabilities as long as the DB follows, and that's not our problem", and then only allow pointing to a single hostname in the DB connection string. Even if I point to an haproxy or SQL proxy, I can't at least point to 2 and have a least one as a fallback. My questions would be : Can Supertokens be configured with multiple PGSQL targets in the connection string ? And before I go down that rabbit hole and test it myself, is anybody using Supertokens with Yugabyte as DB backend in production?