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

I just setup Supertokens and got it linked with my db and I got the init command added to my api. Do I have to create all the routes for my API or is there something i'm missing?

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

hi, i faced an issue.

Error: SuperTokens core threw an error for a POST request to path: '/recipe/accountlinking/user/primary' with status code: 402 and message: Account linking feature is not enabled for this app. Please contact support to enable it.

hi @rp_st I test endpoints via postman. For this, I need to refresh tokens at regular intervals. Is there a token for postman that does not require refresh?

Hi Supertokens Team, I hope this message finds you well. I am currently working on integrating Supertokens into my application, which consists of Vue.js on the frontend and Nest.js on the backend. Initially, I successfully implemented the Supertokens login functionality using the SaaS version, and everything worked smoothly. To facilitate local development, I decided to switch to the Docker version of Supertokens by setting up a local instance and updating the connectionUrl accordingly. After successfully completing the setup, including table creation, both the Supertokens core and database containers appear to be running correctly on my local environment. However, upon switching the backend's connectionUri to the local URL, I encountered an issue. The login form displays as expected, and I can successfully log in with Google authentication. However, instead of being redirected to the application's homepage, the Supertokens session refresh logs continuously appear, causing an infinite loop. When I revert the connectionUri to the SaaS version, everything functions correctly. I've attached a portion of the logs generated endlessly on the frontend for your reference. Could you please provide guidance on what might be causing this issue? Any insights or suggestions would be greatly appreciated.

Hi, I was wondering is it possible to implement Microsoft / Outlook SSO with supertoken? And if yes, where can I find some resources about that?

And if possible to have a “drop in replacement using OAuth” for what we have today, is there an architecture where: The user hits login -> redirect to a service that’s using SuperTokens+Jackson under the hood, they login, we issue an Access Token, RT/Cookie, and issue it to my front end? And then on the backend I can point it at a JWKS for a token verification?

When I access the application in firefox, I get an error "Please provide a valid domain name" in the frontendConfig section.

I'm building the nextjs 13 app but not able to integrate this because of _app.tsx and I've layout.tsx and few things didn't working in client side but supertokens need 'use client' anyone faced similar issue? please help me