Hi Does anyone already implement SuperTokens with Redwood? I can't find any docs about it 😦

Yo yo how do I delete

SuperTokens Managed Service

?

I am customizing the SignUp form fields. How do I add a "Select" dropdown?

Has anyone hosted the core supertokens on AWS lambda?

Hi! I'm trying to implement a custom provider for reddit. Details in the thread

i am setting up SuperTokens with docker-compose but when SuperTokens starts it says that is using memory storage this is my docker-compose file:

psql:
    image: postgres
    container_name: postgress
    restart: unless-stopped
    ports:
      - "5432:5432"
    volumes:
      - ./docker/psql/data:/var/lib/postgresql/data
    environment:
      POSTGRES_USER: ${POSTGRES_USER}
      POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
      POSTGRES_DB: ${POSTGRES_DB}

  supertokens:
    image: registry.supertokens.io/supertokens/supertokens-postgresql
    container_name: supertokens
    restart: unless-stopped
    ports:
      - 3567:3567
    environment:
      POSTGRES_USER: ${POSTGRES_USER}
      POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
      POSTGRESQL_DATABASE_NAME: ${POSTGRES_DB}
    depends_on:
      - psql

and yes i started the db first

See NextJS section -> session verification -> ssr method. Even if you are not using NextJS, you can do something similar

Hi, we have successfully implemented passwordless authentication in our application. Now we would like to disable the registration of new users, so that only the login works and not the registration. We have implemented the following in the Nestjs backend:

Passwordless.init({
          override: {
            apis: (originalImplementation) => {
              return {
                ...originalImplementation,
                createCodePOST: async function (input) {
                  const existingUser = await Passwordless.getUserByEmail({
                    email: (input as { email: string }).email,
                  });
                  if (!!existingUser) {
                    throw new ForbiddenException(
                      'Creating a new user is not allowed'
                    );
                  }
                  return await originalImplementation.createCodePOST(input);
                },
              };
            },
          },
          ...

Now this works fine, but in the frontend I don't see the error message

Creating a new user is not allowed

but

Something went wrong. Please try again

. Now 2 questions: 1. is this the right way to deactivate the registration of new users in the passwordless authentication? 2. how can I override the default error message in the FE? Thanks a lot 🙂

Good afternoon! I am trying to follow the guide here to retrieve a userID: https://supertokens.com/docs/emailpassword/common-customizations/get-user-info however typehinting the req and adding a ! into the statement is causing a syntax error. How else can I grab the user ID?

Are the frontend auth routes from the NextJS SDK Next-specific or able to be used with any backend as long as the config is set correctly? As far as I can tell it seems like everything just uses the same stuff from the React package, with some extra stuff added for routing & SSR support But... I'm deploying on Vercel with a Next frontend but a backend api written in a different language (Python, FastAPI), and I can NOT get APIs nor signout to work correctly for some reason. Signup and signin works fine, but trying to call any backend service from the browser with an axios request throws 401. I've tried wrapping axios outside the component function and inside useEffect(..., []). Also, after calling logout, going to /auth again doesn't redirect to the signin screen unless I manually clear browser cookies. Protecting a page with the ThirdPartyEmailPasswordAuthNoSSR also doesn't redirect to signin after I've signed out, unless I manually clear the cache. The backend endpoints work fine when tested from Insomnia. I thought it might just be an issue with dev mode but I've tried fully building it too.