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 curtidas
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 curtidas
Eu tive a mesma pergunta. Por que o password_hash (ou salt) ainda está definido no banco de dados para uma conta registrada através de provedores OAuth (eu uso o plugin Discourse OAuth2 Basic)? Meu experimento prova que os usuários conseguem fazer login (se não desativar “habilitar logins locais” quando OAuth2 estiver habilitado e configurado) através de sua senha local que foi definida através de funções de redefinição de senha em seu painel de preferências. Eles também podem fazer login através de suas credenciais de provedores OAuth2. Ambos os mecanismos são permitidos, como pfaffman disse.
Estou curioso sobre qual Ă© o valor bruto inicial do password_hash?