116 results found
-
Session Management & Device Visibility for Firebase Authentication
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
26 votes -
Enable Firebase Authentication Pre-PIN Entry on Android Devices (Android direct boot aware SDK)
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:…
67 votes -
Firebase Auth with IP address whitelist & blacklist
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.
5 votes -
1251 end
VIP NUMBER
1 vote -
সাইন-আপ
সাইন-আপ
1 vote -
1 vote
-
Firebase Auth Expose Email Verification Status and Attempts
Firebase Auth Expose Email Verification Status and Attempts
We have a user that is having problems verifying. However there is no logging or debugging for this feature on firebase.
- Add an interface under auth to see which users have requested verification
- Add information about if the email was recieved, spammed, blocked, expired
- Visually show which accounts are not validated, pending validation, and validated.
- Be able to reset validation, or manually validate
1 vote -
Native support for RBAC (Role-Based Access Control)
Native RBAC (Role-Based Access Control) management
Currently, to manage roles (admin, editor, client), you have to use Custom Claims via the Admin SDK (Node.js) or store the roles in Firestore. This is cumbersome for a beginner.The improvement: Being able to define roles directly from the Firebase console and have them automatically appear in the
request.authobject of Security Rules without additional code.1 vote -
Improve Firebase Auth integration with Server side rendering (Next.js)
Hey, hi, I’m a Next.js developer, and the only problem I’m having with Firebase is with the Firebase Auth integration. I’d like to see improvements to the documentation for Next.js and its integration with server-side rendering. The problem I’ve encountered is that we need to save the token generated on the frontend to pass it to the backend. And the Next.js documentation recommends creating the token on the backend as “HttpOnly” for better security, but Firebase Auth doesn’t follow this pattern, and there isn’t much documentation about it or how Firebase handles cookie security.
I hope Firebase will consider my…
1 vote -
BUILD
LOVE
2 votes -
Any one hacke my phone automatically attacks how track that devices totally collapsed
Hel that himself completely distracted.
Only one system connected.4 votes -
Multiple Roles
As of now, firebase only supports single role. We want multiple role support. Example, Employer, Employee, Admin etc.
3 votes -
1 vote
-
Support for One-Time Code (Passwordless) Login
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.
3 votes -
Support adding a note to each authorized domain in the auth settings
We have a lot of authorized domains added by different team members. We'd like to remove unused ones, but we have no idea which ones are actually being used or why they were added. It'd be great if we could add a note to each item for future reference.
1 vote -
Request to Enable Firebase Phone Authentication in Somalia.
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.
3 votes -
Pre-built User Authentication & Common App Features
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…
5 votes -
Firebase Authentication Setup API
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.49 votes -
Add Native Invitation Email Flow for Firebase Authentication (Multi-Tenant Apps)
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 -
Save phone
Idea save
1 vote
- Don't see your idea?