Hi, I tried running supertokens (the binary) in aws lambda and it doesn't seem to work. What I did was I downloaded the supertokens-postgresql binary, dockerize it by copying the binary over to the docker image and installing it there. I tried to "docker ps" into it and ran "supertokens start" and it worked. However, when I deploy the image to AWS lambda it fails to run everytime. Hence, I set the erro flag in config.yaml to "null" so that the error would show in std-in, and what I found was always a java exception, something related to read-only file system. I suspect this is because aws lambda has the entire file system as read-only, except for /tmp. But Supertokens is trying to write to /usr/lib/supertoken/webserver-temp. Any idea about this? I essentially tried to run "supertokens start" when the lambda function is triggered but failed to do so.

It looks like SuperToken cookies are exceeding the permitted limit. I'm getting this error: "Set-Cookie header is ignored in response from url: http://localhost:4000/auth/session/refresh. The combined size of the name and value must be less than or equal to 4096 characters."

Hey, in the EU the information about Terms of Service and Privacy Police not allowed with only info text, the user should be activ opt-in like a checkbox. Actually supertokens only shows an infomation text. With the formFields option i can only add text inputs, is that so? How can i change this to an checkbox? Also it would be nice if the form type was like JsonSchema7 so you can add dynamic all fields, proofs and types you want. https://jsonforms.io/api/core/interfaces/jsonschema7.html

Automated tests with pytest

How do I login manually? Using a custom login page

Hi team, I'm actually facing a problem.. I have a postgres instance running on a seperate container, and I want to connect supertokens container to the postgres container. I think I am facing issue at POSTGRESQL_HOST.. This is my docker command: sudo docker run -p 3567:3567 -e POSTGRESQL_USER="postgres" -e POSTGRESQL_PASSWORD="postgres" -e POSTGRESQL_HOST="host" -e POSTGRESQL_PORT="5432" -e POSTGRESQL_DATABASE_NAME="supertokens" -d registry.supertokens.io/supertokens/supertokens-postgresql This is my postgres docker-compose.yml: version: '3' services: db: image: postgres:latest environment: POSTGRES_USER: user POSTGRES_PASSWORD: pass POSTGRES_DB: supertokens ports: - 5432:5432 networks: - db restart: unless-stopped supertokens: image: registry.supertokens.io/supertokens/supertokens-postgresql depends_on: - db ports: - 3567:3567 environment: POSTGRESQL_CONNECTION_URI : postgresql://user:pass@db/supertokens networks: - db restart: unless-stopped networks: db: driver: bridge

Hi there, I'm getting this error on the react client:

Access to fetch at 'https://evt-api-dev.revod.cloud/auth/signinup/code' from origin 'http://localhost:8000' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'.
evt-api-dev.revod.cloud/auth/signinup/code:1          Failed to load resource: net::ERR_FAILED

even though these are the allowed origins in the nestjs backend:

ts
app.enableCors({
    origin: [
      process.env.EVENTVM_BASE_URL,
      'https://studio.apollographql.com',
      'http://localhost:8000',
    ],
    allowedHeaders: ['content-type', ...supertokens.getAllCORSHeaders()],
    credentials: true,
  });

why's so?

When I tried to sign up with my new custom field it fails with the response:

json
{
    "message": "Are you sending too many / too few formFields?"
}

What are the causes for this? What do I need to provide?

Can I share tokens somehow between subdomains? So let's say I have app.todolists.io and admin.todolists.io so I can do some user management or whatever in the adminpanel. Can I share my login between those two apps so I don't have to reauthenticate? (and maybe I would have an account.todolists.io for language and theme preference for example, or to enable 2fa in the future ;-))

Hey! It's been asked before but I can't see the answer. Any plans on supporting passkeys?