102 results found
-
Firefox extension support with Firebase Auth
I have created a chrome extension using firebase auth and I am trying to create a Firefox version of the chrome extension.
It seems that Firefox extension domains (moz-extenion://) are not allowed to be added to authorized domains in firebase making it not possible to using firebase auth I am assuming.
Is this simple feature addition in the pipeline - to allow web-extensions (not just chrome) domains to utilise firebase auth?
Are there any other workarounds?
1 vote -
Have authentication that works
Auth is down, verified across many production apps, but the status page shows auth is up.
Error Unexpected error using Google for login: FirebaseError: Firebase: Error (auth/missing-project-id)..
1 vote -
Add more auth built-in auth methods
The way that Firebase helps developers quickly setup OAuth providers is amazing, but it would be really helpful if there were more providers to choose from. I'm sure you could do it if you set things up yourself, but making it easier to use services like LinkedIn would be really helpful.
2 votes -
Firebase Authentication support for Ionic Cordova via phone login on IOS.
Unfortunately, phone authentication using the Firebase JS library is not currently supported in Cordova/Ionic environments. This limitation is due to the use of the file:/// protocol, which prevents reCAPTCHA from verifying the origin of the application. As a result, reCAPTCHA cannot function properly.
We would like it to be available in such environments.
1 vote -
Microsoft SignInWithCredential functionality
To add authentication a manifest v3 chrome extension SignInWithCredential has to be used as SignInWithPopup violates the v3 csp rules.
Microsoft tokens currently aren't supported, making it hard to use Microsoft authentication in a chrome extension unless you create a backend cloud function. This is a long workaround and would be helpful if SignInWithCredential could be used immediately.
1 vote -
The errors thrown for a wrong password and an account that does not exist should be different
This is a problem I have encountered while using Firebase with Swift. I want to be able to prompt the user to sign up if they do not have an account. However, the error returned from Auth.auth().signIn(withEmail, password) is the same if the user enters the wrong password or an email the doesn't exist. If the errors were different I would be able to show the sign up prompt only if that specific error is thrown.
2 votes -
Another project contains an OAuth 2.0 client that uses this same SHA-1 fingerprint and package name combination
Hello everyone,
I'm facing a persistent issue when trying to register my Android app in Firebase, specifically related to the SHA-1 fingerprint. My application is built using React Native.I recently cleaned up my Firebase console by deleting several old projects, leaving only one active project named socialapp. My intention is to add my React Native Android app to this socialapp project.
When I attempt to add an Android app to my socialapp project in the Firebase console, I consistently encounter the following error message:
Another project contains an OAuth 2.0 client that uses this same SHA-1 fingerprint and package…1 vote -
Support for Customer-Managed Encryption Keys (CMEK) & Sovereign Cloud
With growing tensions between the US and EU, European enterprise customers' concerns about data privacy are growing.
In order to continue using Firebase as a core technology stack, customers are demanding additional assurances, such as CMEK or even externally managed encryption keys (like those managed by Thales or T-Systems).
Often, those enterprise customers are major revenue drivers, making service providers dependent on Firebase question their choice of Firebase as their infrastructure.
This can be a primary driver for adoption away from Firebase services as a whole to different services or platforms.
1 vote -
Customise or remove domain (firebase.com) from Firebase OTP message.
We are using Firebase authentication for sending OTP's to users.
Currently the OTP message contains the text: "Your OTP is 123456. Sent via com.myapp.firebase.com"
Our team would like to remove or customize the domain reference for branding and user trust reasons. We feel this part can confuse users or make the message looks suspicious. Please allow developers to either:
Remove the domain
Replace it with custom branding
This change will help improve use trust and experience in production apps.1 vote -
Use readable date format for email sign-in
According to
https://firebase.google.com/docs/auth/web/email-link-auth#default-email
and
https://github.com/firebase/firebase-js-sdk/issues/2574
The email sign in template contains a timestamp in the email title and body, so email are not collapsed into a sigle thread.I believe the current date time format, such as 2024 November 11 13:33 UTC is not user friendly, and should be replaced with a more readable format, such as Nov. 11, 2024, 11:33.
The mail language is already based on the language set in the Firebase Authentication -> Template language section, so the formatting can be done based on the same setting, or a new option can be added in the Firebase…
5 votes -
Deactivate the automatic sending of the email template with a checkbox
Hello everyone,
currently not all email templates can be changed. For example, when activating multifactor authentication, you have to be satisfied with the ugly automatically generated email from firebase. It would probably be an easy to implement development if you could deactivate the automatic sending of the email template with a checkbox. Then you could implement your own email dispatch. Please provide a way to disable the automatic sending of email templates.
Thank you and best regards
1 vote -
Allow configuring standard Firebase Authentication via Terraform
The google Terraform providers allow creating and configuring Firebase projects via Terraform.
This includes Firebase Authentication via the googleidentityplatform_config Terraform resource, but also forces an upgrade to Firebase Authentication with Identity Platform.
Identity Platform has a much higher cost.
We'd like to be able to configure standard Firebase Authentication via Terraform
5 votes -
Suggestion for Enhanced Authentication Flow in Firebase Authentication
Dear Firebase Support Team,
I hope this message finds you well. I am reaching out to share a suggestion that I believe could greatly benefit Firebase Authentication and developers working on more complex applications.
Currently, Firebase Authentication provides excellent flexibility with signInWithPhoneNumber and createUserWithEmailAndPassword, allowing projects to authenticate users using either a phone number or an email/password combination. However, in certain projects, both the phone number and email/password are essential to meet higher security standards and user profile requirements.
In these cases, having an integrated authentication flow that combines signInWithPhoneNumber and createUserWithEmailAndPassword within a single, cohesive process would be highly…
4 votes -
multiplatform
full support for KMM android, web, ios and desktop.
What is the point of not supporting all of these?we build the best car but you can only use one wheel. Not a great theory for adoption.
1 vote -
4 votes
-
API Revoke Token
Simple API to revoke the token/refresh token from a backend without using the SDK.
19 votes -
Share phone number with project if Firebase knows that number via another project
Would be a HUGE cost saver given the increased pricing of SMS multi factor authentication.
If Firebase knows the phone number / email via another project, offer the app user to share their phone number with this app and skip costly SMS verification.
2 votes -
Firebase authentication needs to support standard user profile attribute mapping
When leveraging firebase for OIDC based authentication, there is data loss in mapping of standard user profile attributes between IdP and app such as given name, family name and other attributes as specified in the standard specifications[1]. Firebase auth must implement the specification properly and ensure against data loss.
1 vote -
Make Phone Auth support MFA
Food delivery services usually need to know the phone number of their customers, to guarantee that the deliveries will be smooth.
So, a food delivery app would probably prefer authenticating users by phone number rather than by email address.
Phone auth on its own isn’t particularly secure, though, so it would be nice to allow users to optionally add email authentication as a second factor.
As of right now, phone auth doesn’t support MFA, though, which means that a food delivery app might want to force users to use email and phone 2FA right away, which might seem intrusive to…
3 votes -
122 votes
- Don't see your idea?