Firebase custom claims as feature flags
How to use Firebase Auth custom claims as server‑driven feature flags, with a concrete Admin SDK setup, client consumption, and propagation considerations.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
How to use Firebase Auth custom claims as server‑driven feature flags, with a concrete Admin SDK setup, client consumption, and propagation considerations.
I am developing a mobile with react-native (react-native-firebase/auth) and using Firebase Auth to manage user login. In the beginning, I only use the email/password to auth users and work nice. Now I would like to let users use Azure AD. Since react-native-firebase/auth does not support Microsoft account at this moment, so I use react-native-app-auth. After
A Firebase project using OAuth redirect or popup sign-in succeeds on localhost because Firebase implicitly authorizes localhost for development, but production origins must appear in the Authentication Authorized Domains list. The list does not support wildcard entries, so ephemeral preview URLs, regional subdomains, or multi-tenant hosts require explicit en
Firebase has announced a new optional upgrade called Firebase Authentication with Identity Platform, however, the new features already exist on the GCP Identity Platform. As mentioned in the documentation here Identity Platform serves as the backend for Firebase Authentication with Identity Platform and the features that are offered are identical. I want to