So I am using

FastAPI

and I would believe that the

Middleware

will add the

/auth

endpoints (set website_base_path) to the fastapi application, but it does not. I dont see any errors though. I tried the example from github, but no success ( https://github.com/supertokens/supertokens-python/blob/master/examples/with-fastapi/with-thirdpartyemailpassword/main.py )

For passwordless recipe implementation using web-js-sdk It's not clear from the docs which fn should I use. There are multiple fn is SDK reference. So I'm just guessing from the fn names that probably these are all the steps/code I need to have for authentication 1. Create passwordless code -

superTokensPasswordless.createCode({ email: "john@example.org" })

2. Now either they will type in the code in a form I provide or they will visit the email link. If they visit the link, I will get their code like this

const userInputCode = superTokensPasswordless.getLinkCodeFromURL()

3. Then I will verify the code -

superTokensPasswordless.consumeCode({ userInputCode: "8465AWETA" }).then((res) => { if(res.createdUser){ console.log(JSON.stringify(res.user))} })

Session should be automatically set now Am I missing anything?

Hey team , I am using managed solution for supertoken and I received "No SuperTokens core available to query". I received this error around 12:54. Was supertoken down during that period . As currently I am not receiving that error and auth is working fine .

@rp_st Hey guys, Do you have an SDK for Remix?

I have both an electron app and a web app that do different things. When I sign in through the Electron app, the Electron app starts showing the webapp. Where can I change this? So that Electron just goes to its own main renderer.tsx file. I found this: https://supertokens.com/docs/thirdpartypasswordless/pre-built-ui/auth-redirection But not sure how I can differentiate web/Electron.

Once client Application send token (generated by SuperToken) to backend API, how backend API will validate the token

Hello! I'm wondering what the timeline is for the 2FA improvements that are listed on the product roadmap? I just started looking at 2FA and the docs have this big Caution banner: https://supertokens.com/docs/mfa/backend/second-factor

I’m running supertokens production. Are the databases backed up? Can I have access to the backups? If I want to migrate to on-prem, can I request a data dump?

Is there a way to self host the resources that the dashboard loads from 'cdn.jsdelivr.net'? No idea why, but sometimes getting bundle.js and main.css from the cdn takes 5+ minutes, which makes development involving the dashboard difficult.

I have a Nextjs application in which I have created a backendConfig file. When I use more than one third party clients (as used in this example: https://github.com/supertokens/next.js/blob/canary/examples/with-supertokens/config/backendConfig.ts), the application starts giving an error

Error: The providers array has multiple entries for the same third party provider. Please mark one of them as the default one by using "isDefault: true".

. I am not sure what to do here.