Optionally require email addresses to be verified

[alfongj]

Provide optional setting to require email addresses to be verified in order for a user to sign in with email and password.

[SUPERCILEX]

This can be done with Play Services 9.6 using FirebaseUser#sendEmailVerification() and FirebaseUser#isEmailVerified().

[samtstern]

@SUPERCILEX good point. I think @alfongj was hoping we could provide this as a SignInIntentBuilder option to fail sign in for unverified email addresses and have some UI to send the email automatically.

[SUPERCILEX]

Yeah, I just wanted to point out an easy way to handle the verification for anyone submitting a PR. The UI part seems like it will be difficult because we would need to check periodically with isEmailVerified and not let let the user in if it isn't. Anyway, food for thought.

[Kurt29]

Hm, was this suggestion about the automated verification email, or more like if you have no invite, you can’t create an account?

[samtstern]

@Eragon29 I think the suggestion to to help with the entire flow:

• If a user tries to sign in but has an unverified email, send them the verification and show some "please check your email screen"
• When the user has verified and returns to the app, we should detect verification and allow them to proceed.

[Kurt29]

@samtstern
Too bad
Would be nice to have a way to manually verify emails. But it’s probably not that important and there are ways to work around this “issue”

[baole]

It would be nice to request email verification in the AuthUI builder, such as

new AuthUI.IdpConfig.EmailBuilder()
.setRequireName(false)
.setRequireEmailVerification(true) // not in the builder atm
.build()

And this library will handle the rest.

[AndrazP]

What is the status of this feature request after almost 4 years?
I just started integrating Firebase Auth and was really surprised after finding out verification emails are not sent out automatically.
It's a basic functionality that Firebase Auth should offer effortlessly.

[samtstern]

@AndrazP no update, I do think this would be useful it's just that FirebaseUI has been focused on stability and adding support for more identity providers for the last few big releases.