Case 1
if account was created using the email and password, in that case email is marked not verifed ( this is fine).
Case 2
if login via OAuth services, and if there was no account earlier with the same email then in that case email is marked verified ( this is fine).
Case 3
Now, when user login again using any OAuth service ( google, facebook, apple), and if email address is same in OAuth provider as well, then in that case email should be marked as verified ( this was expected behaviour).
Wonder, why in the case 3 email is not getting marked as verifed when user logging in via OAuth and if account already exist with given email address?
Iβm going to guess it has something to do with separate Identities?
logging via OAuth doesn't tend to create new identity...
Identities are something new in 1.4. we haven't documented them yet π
so just doubt would it create new Identity, but what if email already exist π€
yap, seems this is it
just wondering, that we will go with case 3 no? that describe above? Would be prevent the OAuth login ( because most of custom server implementation does prevent user from Logging if accund was created via email password)
Case 3
Now, when user login again using any OAuth service ( google, facebook, apple), and if email address is same in OAuth provider as well, then in that case email should be marked as verified ( this was expected behaviour).
Recommended threads
- Download appwrite Docs
Is there is a way to download appwrite Docs ? Because appwrite skill isn't enough to give the agent full understanding about how appwrite works (I noticed this ...
- How do you contact support to cancel a s...
My nephew signed up with my CC without my permission and has forgotten the password to the account. I can't for the life of me get a hold of anyone at appwrite....
- I have try to use the appwrite in to the...
Invalid Origin. Register your new client (oailedjdbkhlkakmnnapoonllbnfmfij) as a new Web (Chrome Extension) platform on your project console dashboard