I just posted to production. Been developing localhost with nextjs. When in production I'm getting this error:

has been blocked by CORS policy: Response to preflight request doesn't pass access control check: Redirect is not allowed for a preflight request.

I'm wondering if it has something to do with

NextCors

middleware? Any ideas?

Hi all, how to use the custom ui for supertokens using reactjs. Can any one share me the demo example on the same. Thanks

Hi, I am facing an issue with Google sign-in, email password sign is working. Below is my config

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 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?

I'm trying to self-host Supertokens Core, but it only works if I run it as administrator on Windows. I'm trying to start it when I start my server via npm's package.json, so I would prefer not to have to run my whole project as admin. How can I make sure that supertokens runs as admin on Windows and sudo on Linux? I've looked at

sudo-prompt

, but I'm not sure how to call it from a npm script like I can call

tsc

,

eslint

,

cross-env

, or

ts-node-dev

.

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