Hi. I have a problem while doing fetch from the front end to my backend I get 401 non-authorize. In docs, it said that if 8using fetch no actions are needed, what I'm missng

Hi, I'm trying to setup auth with my chrome extension, I've browsed past questions about this problem, and it seems the most straightforward solution is to use jwt with localstorage. But there's a couple things I'm still wondering: - I've tried setting the

cookieSameSite

option to none, and I can see that it is indeed set with the option, however, when launching request from the extension, the cookies are not there, why is that the case ? - If choosing to use the jwt with localstorage approach, does it mean that refresh the session does not work anymore ?

Noticed that the api-key specified for the super token core is getting added in to the request header at the client side, wondering if this is right behaviour since I thought that the back end node app is proxying the call to super token core.

hey :). we are having an issue with the redirect uri returned for Apple on the web. the code that creates the redirect uri uses the API base path instead of the UI base path.

Blegh, trying to login with google auth, im getting a 500 response.. Can't figure out why Anyone has any idea: my server logs:

shop-web:dev: error - Error: Request failed with status code 400

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

Hi team I'm running into a new CORS error we haven't had in the past. The CORS configuration is now blocking requests between our api (express) and client (react) with the error message: "Access to fetch at 'https://vms-api.macleanengineering.com/auth/signin' from origin 'https://vms.macleanengineering.com/' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled." We've set out cors configuration according to the user/password user guide so I'm starting here. Here's our current cours config: app.use(cors( { origin: ['https://vms.macleanengineering.com/'], allowedHeaders: ["content-type", ...supertokens.getAllCORSHeaders()], credentials: true, } ));

Folks, I'm struggling to have it working, but the problem is not really SuperTokens but Apollo Server. I'm trying to use subscriptions, following this guide (https://www.apollographql.com/docs/apollo-server/data/subscriptions/#enabling-subscriptions). It "works" but I can't put SuperTokens' session in the context. Any suggestion ?

Super Tokens Core (self-hosted) and postgreSQL: password authentication failed