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
- Excessive usage of cloud functions is sl...
I have made almost all my requests through cloud functions and jwt , due to security fears of a user editing a field he is not supposed to . This unfortunately...
- Using Binary Log with Appwrite
If I can remember correctly appwrite uses mariaDB as the underlying database. If so could I use mariaDBโs binary log to see database operations from appwrite?
- Project Inactivity Clarification
I'm on appwrite free plan with my account (om.thakkar@ivcventure.com). Even though throughout the week we use the project atleast once to upload dynamic content...