Hi, Our current functionality is build on Flask, but flask is not supporting Async completely which is required for one of our requirements. So, we were planning to move to Quart framework. So, the question is, SuperTokens support Flask, FastAPI and Django REST framework Out of the Box. Can we do to run SuperTokens on Quart as well?

Hey @rp_st for older version of supertoken node - 12.x.x , do we have multitenancy as the recipe ? const Multitenancy = require("supertokens-node/recipe/multitenancy"); I couldn't find this file. Its throwing an error.

Good afternoon! I'm looking at using Okta with the ST Passwordless recipe. I'm using a PKCE flow without a client secret, and getting this error

Please provide the oktaDomain in the additionalConfig of the Okta provider.

. Is this flow detailed somewhere in the docs that I can reference?

Is there a way to auto set primary user on sign-up? Otherwise I override signInUp on backend and call createPrimaryUser

Block specific email domains: We're getting a lot of sign ups from protnmail, simplelogin, suremail, mailbit, passinbox, 8shield, and other secure or temporary email services that lower the quality of our users. Is there a way to set a list of "do not allow" email domains for email sign up? I know a lot of sites do detection on the email domain during signup to make sure you're using a "good" email. It would be better if there were some sort of proactive feature to signal email address "quality" during signup, but a s imple "do not allow" list would probably do the trick at least for now. Though there are hundreds of these types of services so might be difficult.

I'm getting 401 not authorized when using verifySession() in an express handler: app.get("/api/market/list", verifySession(), rateLimiter, asyncHandler(async (req, res) => { This is across subdomains. I'm calling domainname.com/api/thingy from dev.domainname.com Any ideas on how to fix that?

hi, @rp_st thirdparty signinup POST request failes with response 404 on specific user. how can i debug this?

Hi, I have a problem with the Session.sighout function. After calling Session.signOut, the session still exists (Session.Session.doesSessionExist returns true). This is the code of my signout function:

javascript
await Session.signOut();
alert(await Session.doesSessionExist())

I am using the supertokens web sdk. Is there anything i did wrong?

how can I implement SSO for my clients with supertokens? They want to sign in with azure AD accounts.

hi.. where can i see my previous billing details in supertoken website