why can you login with provider but not create user with provider?
See original GitHub issueHi,
When I use a provider (in this case google) I would like to createUser automatically using the details available in the auth.
However createUser requires email / password.
If your using the federated oath method why the need for password?
couldn’t we simply use email / uid ?
If I manually create a user with key matching auth.uid logging in successfully finds the nominated profile.
If I then go and remove permission to the app in my google account, then login and give permission again the generated uuid remains the same, i.e. the old record for the previous permission still exists in the firebase auth.
So wouldn’t it be possible to also create user with: { provider: 'google', uid: 'mLHxB1FGmSg5bIkSB5PnmyWlceo2'}
as credentials when using federated oath?
Id like to be able to automatically create a profile via createUser when a user logs in via a provider if no profile for that users uid exists yet.
I don’t quite see the point of supporting provider based login if the user still has to do an app specific email / password signup to be able to use the profile feature.
Granted I have only used the google provider but I assume at the firebase auth db level the records are all the same
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (3 by maintainers)
Top GitHub Comments
Using popup seems to work version 1.1.5
react-redux-firebase
are you currently using?Use
popup
for now (the default if you don’t pass type). It seems that Firebase has changed their API slightly in recent updates, which has caused redirect to not work correctly. I have been in contact with someone at Firebase talking over the best way to address this issue (apparently due to not using a script tag).