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.

Hello! I'm following https://supertokens.com/docs/emailpassword/custom-ui/init/backend with a fastAPI+Postgres. Should the

/auth

routes be visible in the OpenAPI

/docs

endpoint if I did everything according to the link above? TIA for any help!

hey i am using thirdpartypasswordless and the user can signin using there phone or email and as per requirement we want to get the user input values in frontend state so please tell how can we get this?

@rp_st i sign in email or password using emailpassword recipe.if password wrong how to block login some time attempts in supertoken?

Hello folks, We are building an open-source platform (http://github.com/agenta-ai/agenta) where we want to include features for authentication. Each of our users hosts our platform in their own instances. We were thinking of using supertokens for authentication. One idea we had is to have one central supertokens core instance hosted by us that is shared by all users of our platform (meaning each user hosts their own instance of agenta, and their agenta backend calls supertokens core hosted by us). This would allow us to measure the real number of our users. Now, the challenge is that means that the supertokens core that we host will be openly available to all the internet without API keys. The question is: what security risks does this present? I understood that the supertokens core provides an endpoint for session creation. However, the backend itself is the one that verifies this session internally. So, if my understanding is correct, even if some attacker used supertokens core to create a session, they won't be able to user this session token in a users backend. Is this correct?

/email/exists endpoint fails for social media accounts. it seems that it only works for email account. any ideas how to impprove (override) it to support social accounts as well?

I am getting this 500 internal server error - custom ui, nestjs backend

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, any guide on how to use Passwordless and Session management in a plain html, js website with flask backend. Is it even possible right now?

Is the email template tied to the SMTPService class? I want to enqueue the email to an HTTP endpoint (also easier to integration test) instead of directly connecting to SMTP