Hi Guys, We got 1 hasura instance and 1 supertoken instance but 2 apps with 2 endpoints

/api/auth

. We have to provide a JWKS endpoint. Is it oké to provide just 1 endpoint?

When hitting 'auth/signinup/code/consume' I want to send additional info like name and consume the same in backend. I'm using api override but any additional parameters I pass are filtered out

Hello 🙂 Is it possible to request password, or use the email/password login, when initial registered with third party I was checking https://github.com/supertokens/supertokens-auth-react/blob/master/examples/with-thirdpartyemailpassword-passwordless/api-server/accountLinkingMap.js But this is not what we want. Basically, what we want is a user that registered by third party, request/reset password and login by email

Hi guys, is there by any chance an Interceptor for Angular yet? 🙂 @martin8

Is there a way to disable the /auth/signup and make it only available to add users through the admin panel?

Is it true, that ``createNewSession`` get's called before ``emailPasswordSignUpPOST`` upon registration? I wanted to store a user in the db using ``emailPasswordSignUpPOST`` and store the information in the session using ``createNewSession``. Weirdly, this illustrations tells the opposite behaviour I am having: https://supertokens.com/docs/thirdpartyemailpassword/architecture

Hi everyone, I was wondering something about the 3rd party + email recipe. let's say someone uses google signin and then tries to signup using the same email address. I notice that in the database there are 2 users created with the same email (and different userids ofcourse) is it possible to configure supertokens to prevent that? I would like to use the email as user id and when the user tries to signup with the same gmail address to get an error about they are being already registered

Question, should I use the same db instance for the entire project or is it better practice to have a dedicated database for supertokens?

@User Looking to move from auth0 completely to supertokens.

Hey again. 😅 Needing some guidance. I have a Svelte-Kit app ("Isomorphic Svelte") that needs to use what I think a blog called "opaque tokens" for authentication. Login is EmailPassword only. Since I'm using Svelte, I have to build out the login UI and functionality on my own. I saw that there are

PATH/signin

and

PATH/signup

routes. But are there any routes that allow me to verify if the user is still logged in from the frontend? I want the routes to be protected on both the backend and the frontend. So the frontend would need to know if the existing session is still valid before navigating to protected pages.