81 results found
-
Login with WhatsApp
Just like phone auth, WhatsApp auth would be greatly beneficial for Asian markets. Users don't need to verify with OTP and us developers get access to their WhatsApp directly for promotion purposes.
3 votes -
Allow enabling Firebase Auth programmatically
Instead enabling Firebase Auth manually, by navigating to the "Authentication" tab in Firebase Console and clicking "Get started", can we do all of this programmatically?
7 votes -
MFA option to "remember device"
User shouldn't have to enter MFA every time logging in on same device. There should be a boolean option remember device for some period of time (somewhere between 2 weeks and forever)
5 votes -
Authentication feature in Android Wear / WearOS application
The ability to handle autentication and registration feature in android wear / wearos applications, using FirebaseUI or the official firebase auth library in gradle.
Ideally, the same features promoted to android apps but in the wearable world, taking in account the considerations related to battery, performance and data fetching and processing applied to wearables.
2 votes -
firebase auth ui react component
Firebase auth ui component was broken. When trying to log in it wil not show the password input field.
1 vote -
4 votes
-
Magic link with phone auth
Create magic links in sent SMS messages so users can click on the link in the SMS and log-in into the app, similar to email magic link auth.
2 votes -
5 votes
-
generateRecoverEmailLink
Just as there is "generatePasswordResetLink" to obtain the link to reset the password, I need a method to obtain the link to recover the email, after an email change.
The same link that is sent in the email when an email change is made using "updateEmail" from the front.
Since without that, there is no way to use Firebase to reverse an email change through a link in a custom email, and I would have to build a complete flow on my website for this.
1 vote -
Security vulnerability on using SHA-1 weak hash algorithm
Firebase using SHA-1 weak hash algorithm. This is being raised as Security vulnerability. Recommended to upgrade the hash algorithm.
2 votes -
Option to enable MFA by provider
There should be an option to turn on MFA for a user for specific provider (e.g., password). Since user's Google signin might have MFA already, it's sort of inconvenient to have extra MFA barrier for Firebase Auth tenant.
4 votes -
Separate/standalone Authentication admin library
Quite often I only need the firebase-admin/auth part of the NodeJS admin library. Especially when separating the application into single-purpose containers/microservices.
However because there is no separate NPM package for the auth part, I need to pull in the entire firebase-admin package, which pulls in a HUGE number of dependencies like @google-cloud/firestore @google-cloud/storage, google-gax, @grpc/grpc-js protobufjs and a multitude of others which are not needed for the auth part.
Much of the other components like Firestore, Storage etc can be used directly from the @google-cloud/... libraries without the entire firebase-admin package.
But there is no separate package for Authentication.
Authentication…
4 votes -
Authentication feature in Android Wear / WearOS application
The ability to handle autentication and registration feature in android wear / wearos applications, using FirebaseUI or the official firebase auth library in gradle.
Ideally, the same features promoted to android apps but in the wearable world, taking in account the considerations related to battery, performance and data fetching and processing applied to wearables.
1 vote -
Setting to disable returning auth error type
Currently errors such as "wrong password", "user with this email doesn't exists" etc are always returned to client. Would be nice to have the option to only return a generic error message to improve security.
3 votes -
3 votes
-
Whitelisted email address for testing with passwordless email link
It would be great to have a whitelisted email address to use for testing, like we have for SMS authentication, to avoid this message:
"[firebase_auth/too-many-requests] We have blocked all requests from this device due to unusual activity. Try again later."1 vote -
Allow developers to enable authentication limit to a certain collection/document(in cloud firestore) and to a certain node (in RTDB)
Currently, there is no optimal way to achieve this. If we could write a cloud function for it, then it'd be great.
1 vote -
Review the revoke token from apple functionality
I'm implementing a Login with Apple and everything went smooth until I had to delete the account. According to Apple guidelines I need to revoke the token. However, in the Firebase documentation it says I should implement the following:
Auth.auth().revokeToken(withAuthorizationCode: authCodeString)
But the revokeToken method is no longer available. I haven't found yet a way to do it.
Thanks,
Jose
1 vote -
Review the revoke token from apple functionality
I'm implementing a Login with Apple and everything went smooth until I had to delete the account. According to Apple guidelines I need to revoke the token. However, in the Firebase documentation it says I should implement the following:
Auth.auth().revokeToken(withAuthorizationCode: authCodeString)
But the revokeToken method is no longer available. I haven't found yet a way to do it.
Thanks,
Jose
1 vote -
2 votes
- Don't see your idea?