Skip to content

General

General

Categories

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

87 results found

  1. The firebase-ui https://github.com/firebase/firebaseui-web seems to no longer be supported. It currently doesn't support the latest firebase versions: https://github.com/firebase/firebaseui-web/issues/1107

    57 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. I'm running the Web/APP builder platform using user's own Firebase. However, when user is creating platform through my service, Authentication setup API is limited to Blaze plans users.
    Please provide the Authentication Setup API also for Spark Plan user.
    Spark Plan user is highly possible to be the Blaze plan user in the future if Firebase provide a contentable user's experience.

    42 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. When using Sign in with Apple, a default button that says "Continue to the app" appears. Please allow some kind of developer choice to either style this button, get rid of it completely (this youtube video https://www.youtube.com/watch?v=rJi_Mo-SdW0 seems to suggest the redirect/popup is not even needed at all and the sign in can happen on the actual login page with only a native apple modal, perhaps the Firebase SDK could allow this kind of flow), or another solution that does not involve an unstyleable button.

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Create a comprehensive solution for authentication that is both client and server using middleware to protect pages. Correctly passing the ID token of the user when needed to API endpoints.

    20 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Currently, Firebase Auth is US only. Because the EU-US-Privacy-Shield is not valid anymore, transferring data to the US is for EU companies not allowed. Therefore, Firebase is not GDPR complaint. Allowing us to choose the storage location (like you can weigh Firestore or Cloud Storage) to use a data center in the EU (like europe-west1, europe-west3 or europe-west4, etc.) would make Firebase much more GDPR complaint (beside the Cloud-Act).

    321 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Currently, SMS verification messages in Firebase Authentication include fixed text elements that cannot be customized. For Netherlands numbers, the message includes "Firebase App" text and a link, while for non-EU numbers, this text is omitted but still includes a link. Because some developers need to align SMS messages with their brand voice, remove links, or meet specific regulatory requirements in different regions, this lack of customization limits the flexibility and usability of Firebase Authentication.

    Implementing a feature that allows developers to customize the text content of SMS verification messages would greatly enhance the service. This should include:

    1. Ability to use…
    19 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 269 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. like lovable+supabase

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Allow setting the experation time for refresh tokens. This is important in environments where security is paramount and would allow for user session to automatically expire after a given amount of time.

    Currently this can be done with some work via the admin API, but seems to make much more sense as a setting, in line with other idPs such as Cognito1 and Auth02

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 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…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. 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.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Simple API to revoke the token/refresh token from a backend without using the SDK.

    19 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5
  • Don't see your idea?