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.

Trying to make a request to my backend but getting back unauthorized. I understand cookies are sent automatically? I previously successfully received the cookies in the response headers of

signup/code/consume

. Also using

'Access-Control-Allow-Credentials': true

on my request to the backend. What am I missing? After receiving the cookies from

signup/code/consume

I should see the cookies on dev tools>storage>cookies, correct? because I don't. Btw, I'm using

fetch

, not

axios

Bonsoir 😀 Is it possible to use it with Appsmith, the open source internal tool builder ? knowing that we cannot install external library on Appsmith

What would be the next step?

Dependencies issues on the backend. Is there a reason for

supertokens-python

not allowing the latest

fast-api

version? (0.75). Installing your package is generating issues downstream. Yesterday I managed to manually install all the packages but now the resulting requirements.txt is 'broken' for my cofounder. Maybe some dependency restrictions could be relaxed?

But when I call SuperTokens.doesSessionExist() it returns false. This should be true after a successful call to /signin right? And the cookies should automatically be set in my browser? I only see one cookie when I use devtools to inspect them (although I'm not sure you can see http-only cookies with devtools??)

Hello, I have a question regarding SuperTokens Core - how to debug issues related to it? App is working fine for me (dockerized), but for my friend which is running it on local machine it's throwing an error "No SuperTokens core available to query" - this occurs while trying to register (I removed post from support-questions)