Skip to content

General

General

Categories

JUMP TO ANOTHER FORUM

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

108 results found

  1. Background:
    Our application relies heavily on Firebase Authentication for seamless user experiences and data synchronization. However, we have encountered a significant limitation when the Android lock screen PIN is enabled. After a device reboot, Firebase Authentication becomes inaccessible until the user enters the PIN. This restriction disrupts our ability to interface with Firebase services immediately upon reboot.

    Issue:
    In discussions with Google, it was clarified that Firebase Authentication support is not available until the PIN is entered. This limitation impacts all our major customers who have enabled the Android lock screen PIN, causing operational delays and affecting user satisfaction.

    Request:…

    60 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. Add optional session management to Firebase Authentication that creates and tracks individual login sessions per user, allowing developers/users to view active sessions with device and operating system information (derived from the User-Agent), approximate location (city/country), session creation time, and last active timestamp. The feature would enable per-device logout and selective session revocation via the Firebase Admin SDK, with optional read-only access for clients to build “logged-in devices” security UIs, while remaining privacy-safe, opt-in, and configurable without exposing raw IP addresses or User-Agent strings.

    View Complete Proposal/Request here: https://gist.github.com/12fahed/42e802890b5b887b93c66d94ceadeb2d

    15 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. LOVE

    2 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. Hel that himself completely distracted.
    Only one system connected.

    3 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. 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.

    47 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. As of now, firebase only supports single role. We want multiple role support. Example, Employer, Employee, Admin etc.

    2 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. Firebase Auth should offer a native one-time code login flow, similar to Azure AD’s Device Code Flow.

    This would allow users to authenticate by entering a short code received via email, without clicking links or relying on deep links, which often fail in desktop or web apps.

    A simple code-based login would make authentication more inclusive, faster, and reliable for all users, especially those without social accounts or using devices different from their email client.

    2 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. Blacklist scenario: Let's say that a device is detected for fraud/scam activity. I want to blacklist the device for 1 year based on the previously logged-in IP address, so the scammer is no longer able to use their devices. Even though the scammer created a new Firebase account, they won't be able to do that because of the IP address blacklist.

    Whitelist scenario: Let's say that I have an internal app. I want this app to be used by my employees only, so only specific devices are allowed to login.

    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. In many multi-tenant applications, an invitation is a time-limited, one-time handshake between two parties inside an app context (e.g. organization, workspace, team, or document).

    After the invitation email is accepted, the link should bring the recipient into the app at a specific contextual entry point (for example, a workspace, organization, or document reference). From that point:

    Existing users continue through the regular sign-in flow (if not already signed in)

    New users continue through the standard sign-up flow

    At that point, the application takes full control of the user experience and logic.

    From Firebase’s perspective, the responsibility would primarily be to…

    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. Idea save

    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 propose adding a suite of pre-built, configurable modules for user authentication and other common application features directly into Firebase Studio. This would allow developers to quickly set up essential functionality without writing repetitive boilerplate code.

    Why this is important: Many developers spend significant time implementing standard features like user registration, login, and profile management. By providing these components out-of-the-box, Firebase Studio would enable developers to skip these steps and focus immediately on building their app's unique and core functionality. This would dramatically accelerate development speed and improve time-to-market.

    Core Features to Include: User Authentication Module: A ready-to-use system for…

    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)
  12. I am writing to request that Firebase Phone Authentication be enabled for Somalia. Over the past two years, there has been significant growth in the use of Flutter and Firebase to develop mobile apps in Somalia. However, the lack of phone authentication support in this region has created a barrier for developers.

    Phone authentication is essential for securing user accounts and is widely used in regions like ours. Enabling this feature in Somalia would greatly benefit both developers and users by improving accessibility and security.

    I kindly ask you to consider this request and enable Firebase Phone Authentication for Somalia.

    2 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)
  13. 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.

    14 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)
  14. I’d love the option to sign in to my app using Discord. Currently, it isn’t listed as a provider, and having this option would make the sign-in experience much smoother for users who rely on Discord. Gemini said several times that it did have discord in the provider list.

    2 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. Adding alternate methods of authentication for Meta apps and google platform like facial recognition and/or eye scanning to make it even more secure 🔐

    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)
  16. We use phone numbers as our primary auth method. We often need to test new user experiences which requires us to create a new account with a real phone number or a test number.

    There are two problems we run into:
    1. A real phone number will be rate limited after multiple logins
    2. Our workaround to (1) is to use test numbers. However, a cap of 10 test numbers is limiting our use case

    We have a GenAI app that is highly personalized for each account. Thus, we often find we need to QA against more than 10 test…

    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)
  17. like lovable+supabase

    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)
  18. For normal apps, one can add the "product" Facebook Login.

    For apps that are categorized as "business", Facebook has this preferred auth mechanism called Facebook Login for Business (ref: https://developers.facebook.com/docs/development/create-an-app/other-app-types#step-3--select-an-app-type)

    However, the latter has more requirements than the former and doesn't seem wo work in Firebase Auth

    Users have to create a Login Configuration (which gives you a configuration id)
    When using the SDK, pass the configuration id:
    Documentation says:
    When invoking the login dialog and setting the redirect URL, include your configuration ID as an optional parameter (although scope can still be included, we recommend that you do…

    2 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)
  19. 2 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. Currently, Apple app links can require up to 24 hours to start working (due to a delay on downloading the AASA files). This can be worked around by using a deep link instead in the form of myapp://mydomain. When links are generated server-side, I can change the form myself, but that isn't possible client-side.

    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)
← Previous 1 3 4 5 6
  • Don't see your idea?