Hey, got a question regarding axios interceptors. Since we no longer need to explicitly set interceptors, how can I choose which axios instance the supertokens chould use? (is that possible) (using vue3 and go)

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?

Anywhere that I could find a example of using Vanilla JS to create custom UI?

how mongodb schema looks like with supertokens?

Hey guys I'm using next js, getting infinite call

/refresh

on Safari (Works fine from Chrome) ``` SuperTokens.init({ appInfo: { appName: 'Test', apiDomain: 'http://localhost:3000', websiteDomain: 'http://localhost:8080', apiBasePath: '/api/v1/public/auth', websiteBasePath: '/auth' }, recipeList: [ Passwordless.init({ contactMethod: 'EMAIL' }), Session.init({ cookieDomain: 'http://localhost:8080' }) ] })

Hi everyone, I need support with django admin page. How do I make default login-password login on admin page work? Or if it is complicated, how do I integrate supertokens auth into django admin page?

Hello ! 👋 I am evaluating Ory Kratos and Supertokens. It looks like both can fit my needs, but my main concern in with the DB high availability part. I'm planning on deploying my app on a k8s cluster and using Yugabyte for the DB, and it seems Kratos does not support it according to some old github issue they had. I'm rather unimpressed with Ory's idea of high availability, which pretty much boils down to "we have infinite horizontal scaling capabilities as long as the DB follows, and that's not our problem", and then only allow pointing to a single hostname in the DB connection string. Even if I point to an haproxy or SQL proxy, I can't at least point to 2 and have a least one as a fallback. My questions would be : Can Supertokens be configured with multiple PGSQL targets in the connection string ? And before I go down that rabbit hole and test it myself, is anybody using Supertokens with Yugabyte as DB backend in production?

We are trying to host our system on GCP. We are using email password recipe and we want to use cloudrun. Just need some pointers on resources that will help to do this or if it is even possible. Thanks!

Hi everyone, I'm trying to add Passwordless authentication using the Prebuilt UI to my React app (using latest versions of

supertokens-auth-react

and

react-router-dom

) but I'm hitting an issue when the app loads:

Uncaught Error: No instance of Passwordless found. Make sure to call the Passwordless.init method

I'm initialising SuperTokens and Passwordless at the root of my application (see thread for code snippets) and I've checked and all the imports resolve to the same module in case they were pointing at different ones and using different contexts so I'm a little confused 😆 . Can anyone point me in the direction of where I might be going wrong please?

I have supertokens core behind nginx reverse proxy. I'm forwarding these headers: proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; I get "hello" only if i remove the Host header. So I'm wondering how to bind the core instance with the A/AAAA assigned record. In the attached docs I found SUPERTOKENS_HOST but it doesnt seem to have effect on the reverse proxy, still getting HTTP Status 400 – Bad Request when forwarding the host. this is my config.yaml core_config_version: 0 host: "0.0.0.0" supertokens_host: "https://supertokens.example.com"