When using the SelfRegistration workflow, a new security setting must be disabled for newly created Firebase projects #170
SchneiderInfosystems
started this conversation in
Show and tell
Replies: 1 comment
-
If have added this information to the wiki: https://github.com/SchneiderInfosystems/FB4D/wiki/Self-Registration-Workflow#disable-the-email-enumeration-protection-within-the-firebase-console-before-using-this-workflow |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Important hint for all application which uses the unit FB4D.SelfRegistrationFra (both FMX/VCL version)
In newly created Firebase projects, a new security check has been installed by default in the authentication settings under UserAction, which hinders the self-registration workflow. This problem also occurs if the self-registration workflow is not used by passing AllowSelfRegistration=false in TFraSelfRegistration.Initialize.
The error occurs within
TFirebaseAuthentication.OnFetchProvidersResp
by raising the exceptionEFirebaseAuthentication.Create('JSON field registered missing')
.This occurs because the FetchProvidersForEMail method does not return any valid data as long as this new security check is active.
Fortunately, there is a simple workaround. This new security check can be switched off in the Firebase Console under Authentication>UserActions>EMail enumeration protection:
Beta Was this translation helpful? Give feedback.
All reactions