SuperTokens is officialy not compatible with Deno, right? Now that Deno added support for npm packages, im wondering: Did anyone get Supertokens to work with deno?

Hello Everyone! :). I am trying out supertokens on angular electronjs with this repo https://github.com/maximegris/angular-electron. During development, everything works fine. However, after I compile into desktop app, launching the application throw an error in console.log “Uncaught Error: Please provide a valid sessionScope” Has anybody experience this or how to solve this?

Hi. Is there any way to change expiration time of tokens depending on the way session created? Now user gets its session using

auth/signinup/code

, then sends otp (we use passwordless recipe)

auth/signinup/code/consume

which gives them tokens. This works fine, but now we want users of mobile app, which we are developing have tokens which will expire after a day, not after several hours as now. TIA.

Is there a recommended way to implement a "remember this device" feature?

what version of supertokens is compatible with asgiref==3.5?

I have another architectural question regarding SuperTokens and its Core. How suitable is the solution for use by multiple services? I would like to use SuperTokens to manage users which are authenticated into multiple apps, and plan on using the UserMetadata recipe as well as UserRoles recipe to store permissions, roles and groups (using the metadata as unfortunately groups aren't part of the UserRoles recipe). My question is particularly regarding some features like initializing recipes and creating all the roles and permissions - from what I can tell I just have to call an initialization method in my service and create all those beforehand to avoid issues later, but if I have to do this in every service just to ensure that the data really exists it seems like this isn't the best approach. How would you go about managing users that are accessed by different apps, and was SuperTokens built for this use-case?

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, } ));

hey @josephmilanmd our sdk does not return a 403 for this route. Maybe something else is doing that on your end?

Hi! One question please: what would be the best implementation for a user with "teacher" role, that wants to create emailpassword users with the role "student" in a customize signup page?

How many parallel logins can a supertokens core and supertokens node can handle in a single core server?