I am using an endpoint that retrieves user data. The matter is that it returns “verified” = 0 for users who used, for example, Google. For login/password it works fine.
To test it, you can send an invitation to a user, so he/she can accept the invitation and use Google as a login mechanism. Then, you use the API, and the response says that user activation has not been completed (verified == 0).
Is there a chance to create a user for you account, and disallow Google/Facebook as an activation options ?
Speaking of account activation via Facebook, when using it, it seems that the label “Waiting for activation” does not got away at all. Plus, in “linked accounts”, there’s no FB icon.
Updated: I found out that such accounts (created via Google only) start returning “verified” = 1 once the admin changes the user’s password. Is that whole thing with “verified” a bug ??
Additionally, I noticed that when I use the link provided above, and specify “login_type” query parameter, it has no effect. For example, it I used Google to create an account, and use recently created id to get the user’s info, it will give me this info regardless what “login_type” I am specifying.