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.

Hey all, is there a way with Supertokens to handle account management ? I have multiple users with different roles (admin, user) linked to one account. These users can only retrieve data from entries linked to that account. Pretty common for B2B apps. How do you deal with that ? Thanks a lot

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

This is one of our components. We have multiple routes. My understanding was that in the if (sessionContext.loading === true) { return null; } if we changed the return null to a loader component, then we could display a loader between our routes but we are unable to see anything even when the route takes time to load. Is there a different way to show loaders?

Hi please here me here how to setup the supertokens. I am using nest I have 2 microservice: M1 and M2 as API gateway. I have setup the supertokens in M1. it takes cred from M2 and signIn. and return Jwt tokens. In M2(no st) when i verify this token in M2 it gives : { "message": "Invalid token", "error": "Unauthorized", "statusCode": 401 }

I am just starting to work with supertokens. I prepared the project as in the tutorial for AWS lambda. I stopped at the 404 problem and prepared the frontend on this init: appInfo: { appName: "SuperTokens Demo App", apiDomain: "https://api.example.com", apiBasePath: "/auth", apiGatewayPath: "/", websiteDomain: "https://frontend.example.com", }, I prebuild UI and i works. When I try type email to sign up I see network issue: Request URL: https://api.example.com/auth/signup/email/exists?email=asda%40dsa.com Request Method: GET Status Code: 404 Not Found But when I opened this page I see response: {"status":"OK","exists":false} CORS works: Request URL: https://api.example.com/auth/signup/email/exists?email=asda%40dsa.com Request Method: OPTIONS Status Code: 200 OK I use the API GW V2 with integration for route: ANY /auth/{PROXY+}

Setting up multiple frontends for one backend for python flask , what value of website domain to keep if we have multiple frontend consuming the same backend , will the origin thing work for python flask as well as mentioned in the docs @rp_st

I have a question regarding the Apple login process. It seems that sometimes the app doesn't prompt me to share my email address. Most of the time, it doesn't ask, but occasionally, it does. What determines this behavior, and how can we control it? Thank you for your assistance.