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 a FastAPI backend and a NextJS frontend. I want to use getServerSideProps to send the logged in user's data to my frontend. When I try to get the logged in user's data in getServerSideProps, I get { message: 'unauthorised' }. I think this is because the cookies in the browser are not sent to my FastAPI backend. Is this even possible?

Hi, is it possible to trigger sending the email verification mail through the backend sdks?

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

Hello This seems like an awesome project. I currently have my users in my mongoDB and logins in google identity management. In the future it would be cool to have everything in mongodb (when the adapter is implemented). My backend is built with c# in asp core. I dont see any mentions of dot net / asp core / c# in the guides or in this discord. Will it be supported or am i the only one who have requested it ?

Bom dia (Good Morning) I am implementing super tokens on django (backend), using thirdparty (only) recipe. I would like your opinions for best practices on how to initialize it. Currently I have a module and using the module config, I'm calling the start method where I have the init function. (I'll attach some screenshots) Still says that it is not initialized

I'm writing microservices in go and want to migrate to using super tokens (self-hosted). What is the "best practice" to authenticate requests on different services? Previously using AWS Cognito which gave me JWKs to validate requests.

I have a question about the Dashboard - is it safe and meant to be deployed in a production? I'm currently using a self-hosted instance, and what sparked this question for me is that self-hosted doesn't require sending the

api-key

header, thus allowing anyone who has access to the supertokens instance to create a new user/change password etc. My assumption is that supertokens instance should not be exposed to the world, and communicated only with via backend. Is that correct?

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?

Hello, I've been struggling to make the setup for Next.js with Edge Functions work. When following the new Next.js setup instructions, using a session guard for an API route works until that route is an edge funtion. To reproduce I updated the example you have linked and added

export const runtime = 'edge';

to the user route https://github.com/supertokens/next.js/blob/canary/examples/with-supertokens/app/api/user/route.ts This now causes the error

Module not found: Can't resolve 'zlib'

(same for

querystring

and

crypto

). e.g. when running in dev or even during build. Which i think is strange since the middleware uses withSession without issues an is supposed to be the same edge runtime. The only "workaround" I found was to tell webpack to stop polyfilling (with config below). But that breaks things elsewhere. Have you (or someone else in here) had similar experiences or a better solution? Any recommendations going forward for Next.js Edge Functions?

const nextConfig = {
  webpack(config) {
    config.resolve.fallback = {
      ...config.resolve.fallback,
      crypto: false,
      querystring: false,
      zlib: false,
    };

    return config;
  },
}