i want to check if the user exists right now appwrite automaticaly creates an account for the user
TL;DR
User is asking why they should check if a user exists before logging in with OAuth2. They are concerned that it may allow bad actors to check if accounts exist on their app. They mention that they want to check if the user exists immediately because their app (Appwrite) automatically creates an account for the user.
Solution: It is generally not recommended to have a feature that allows checking if accounts exist on your app before logging in with OAuth2. However, if you still want to implement this feature in Appwrite, you can modify the code to perform a check for user existence before creating a new account.Why? It's typically not a good idea to have something like that because then bad actors can check if accounts exist on your app
Recommended threads
- Magic Link woes/noob
Magic Link is working; it sends the link to my email. But the link itself always leads to "Page Not Found. The page you're looking for doesn't exist". Clicking ...
- is `account.get()` safe to be used in th...
I want to user's `id` for authentication. However, a while ago I was told in this server not to use `account.get()` and instead add user preferences for that us...
- Usage of the new Client() and dealing wi...
Hey guys, just a quick one - we had some web traffic the other day and it ended up bombing out - To put in perspective of how the app works, we have a Nuxt Ap...