What in the facebook API becomes the password_hash and salt when a user signs up and authenticates using facebook?
They are remain empty.
I thought there was a portion of users who – if they have their facebook settings set a specific way – could possibly both authenticate using facebook and also set a password.
I think that’s my problem. Or I might have a different problem.
Either way I have a user with Facebook() as a login and a password_hash/salt in the db.
Edit: I just checked with a dummy facebook acct. A password_hash and salt are still being set at registration if I use facebook. So something on my end might be drastically wrong I just don’t know what.
I am not following.
It doesn’t matter at all. You don’t have chance to set password when using an OAuth services if they provide username and email.
The user can use their setting page to reset their password.
3 Likes
Users can authenticate against any of the available mechanisms. As long as the email is the same, a single account can authenticate against Google, Facebook, or a local password. Does that explain what you are seeing?
3 Likes
I had the same question. Why the password_hash (or salt) still set in DB for an account registered through OAuth providers (I use Discourse OAuth2 Basic plugin). My experiment proves that users are able to login (if one doesn’t disable “enable local logins” when OAuth2 is enabled and setup) through their local password that set through reset password functions in their preference panel. They can also login through their OAuth2 providers credentials. Both mechanisms are allowed as pfaffman said.
I’m curious what’s the initial raw value of password_hash?