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?

Hello. I would like to know if supertokens currently supports Clouldflare Workers ?

Has anyone successfully setup supertokens with nestjs + graphql? I've had no trouble setting it up for nestjs without graphql, but I'm not able to adapt the supertokens graphql guide to work with the nestjs grapqhl module.

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?

Hi all, I'm new to SuperTokens. I'm using PasswordLess authentication. I have followed the recipe. I do have a nice Sign In which is quite straightforward and works well, thanks for that! However, I don't have any *SIGN UP * and I don't get why. I added the first users through the Supertokens UI. I'm using NextJS. My back-end config is the following :

return {
    debug: true,
    framework: "custom",
    supertokens: {
      connectionURI:
        process.env.SUPERTOKENS_URI || "https://try.supertokens.com",
      apiKey: process.env.SUPERTOKENS_API_KEY,
    },
    appInfo: appInfo("backend"),
    recipeList: [
      PasswordlessNode.init({
        flowType: "MAGIC_LINK",
        contactMethod: "EMAIL",
        emailDelivery: {...}
      }),
      SessionNode.init(),
      Dashboard.init(),
      UserRoles.init(),
      UserMetadata.init(),
    ],
    isInServerlessEnv: true,
  };
};

Could somebody help me?

Hi, I'm looking for info as I have to choose between cookie based/jwt login. But I cannot find right documentation. I have a multitenant, microservice ecosystem, with multiple (web) frontend apps and multiple apis. Once I login in a single frontend app, I must be authenticated in all frontend apps. I have a dedicated supertokens backend microservice (with core hosted internally) where I actually do authentication. No user is shared between different tenant. I cannot use (and I do not want to do it) supertokens SDK in all my backend microservices exposing api (they are a lot, in many different languages). What's the correct choice?

Hey there, i'm implemanting a creation of user profil on my own database while a user is signin up. The user is created after the originalImplementation of my signup, and use some additional fields. My issue is, if there is an error in my database interaction, the user is still created in supertokens, and I can't do it before the supertokens signup because i need the user id. Is there a way to revert the user creation if is there any error ?

hello, @rp_st , I have multiple frontends, and they are entirely different base domains, how can I make supertokens work? I already used header based auth. The point is multiple frontend uses the same project, means same supertokens config.