Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MFA with multiple tenants support #6366

Open
john-hutchinson opened this issue Oct 10, 2024 · 1 comment
Open

MFA with multiple tenants support #6366

john-hutchinson opened this issue Oct 10, 2024 · 1 comment
Labels
api: auth type: question Further information is requested

Comments

@john-hutchinson
Copy link

john-hutchinson commented Oct 10, 2024

MFA with multiple tenants support

iOS
Is not supported according to this documentation: https://firebase.google.com/docs/auth/ios/multi-factor
But registering a user on multi tenant, adding the phone 2FA, and logging in with the 2FA challenge fully works.

Android
Is not supported according to this documentation: https://firebase.google.com/docs/auth/android/multi-factor
But registering a user on multi tenant, adding the phone 2FA fully works.

Only logging in and doing the 2FA challenge fails with error:

[SmsRetrieverHelper] SMS verification code request failed: unknown status code: 17499 INVALID_PROJECT_ID:Project ID does not match MFA pending credential

The strange thing is that on Android, adding the 2FA works (the SMS with the verification code is sent, and verified correctly). but doing the login with 2FA challenge does not (which is essentially receiving a verification SMS again and verifying the code).
Essentially no new functionality is used in login versus registration so it should be easy to fix and fully support.

Question:
When can we expect official support of multi-tenancy 2FA on Android and iOS
And when can we expect (unofficial) support of multi-tenancy 2FA on Android (since unoficially it already works on iOS).

@google-oss-bot
Copy link
Contributor

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

@lehcar09 lehcar09 added api: auth type: question Further information is requested and removed needs-triage labels Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: auth type: question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants