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
- Free plan Usage
I using a free plan with one organization. I have three projects but on the free plan I should be able to have 2 projects running But in my case only 1 out of ...
- Issue with downloading large files (40GB...
Hi everyone! I am using the latest Appwrite 1.8.0 version on my self-hosted server. I successfully uploaded a large ZIP archive (~40GB) using the chunked uploa...
- Beginner Unity game
In tutorial creator get new words, but i dont I dont lnow what problem https://www.youtube.com/watch?v=vQY4jsho1nQ 11:17