Repository navigation
馃殌 [auth] Allow setting custom auth domain for default app聽#8280
Description
#7530 added support for setting the auth domain when calling initializeApp, but since we never do that manually for the default app that solution doesn't help in that case. #7523 (comment) claims that you can set it through your GoogleServices-Info.plist/google-services.json instead. Correct me if I'm wrong, but this doesn't seem to actually be the case. https://cloud.google.com/identity-platform/docs/show-custom-domain#java only shows ways to do it at runtime and I haven't gotten it to work through the config files.
For this reason it would be useful if the auth instance exposed something like a setCustomAuthDomain function that took in the auth domain and just proxied to those native functions to set it.
Activity
mikehardy commentedon Feb 7, 2025
I think you're right, I don't see the current code for setting custom auth domain hooked up for default app anywhere
Not sure how best to handle this while maintaining fidelity with firebase-js-sdk API as there is a real mismatch here between firebase-js-sdk (where you pass it in config for FirebaseApp with no Auth API usage) and native (where you set it directly on Auth, and App does not know about it).
We could just expose a native-specific Auth method as you mention and that seems like a reasonable fallback position, however the ideal solution would be to keep it in the config as mentioned in upstream docs and as used for secondary apps, and just handle it somehow.
Resolution of this choice depends on some analysis to see if we can get the low-level config from google plist/json for the default app in ios and android bootstrap, and if it still contains
authDomainif set. If we can do that then we can handle this via config. If not we'll need a native-specific API on Auth as you mention I thinkmikehardy commentedon Feb 17, 2025
I did a little more analysis on this, findings:
1- - the native "options" objects you use to configure the native FirebaseApp's do not have space for authDomain
2- - the android google-services gradle plugin won't copy it into the app anywhere
What I take from the above two items is that we cannot just counsel people to add
authDomainto google-services.json and GoogleServices-Info.plist - the extra configuration element will not be used or even included in the app, and we are not able to access those files from either native or javascript context in the react-native-firebase module anyway.So adding it to native config is out.
3- the native FirebaseApp configure methods (at least iOS...) do not allow you to call them multiple times
Thus, it's a little unnatural to call it again at the javascript level, however it is possible, and we could add logic to our FirebaseApp.configure method to see if there was an
authDomainelement, and handle it appropriately if so - even if the default app was already configured.Upside to this is that it's how the firebase-js-sdk configuration options looks in the first place, so ... maybe it makes sense
The only other alternative is to directly expose a react-native-firebase-only API like
setAuthDomain(<auth>, <domain>)Between the two, I lean towards firebase-js-sdk fidelity so I'd go with requiring a second configure call at app startup with authDomain in the config object to match firebase-js-sdk
mikehardy commentedon Feb 17, 2025
Okay, final analysis for the day, the first spot to change to implement authDomain for default app, assuming we go with firebase-js-sdk compatibility and we require
authDomainin the config object and call toinitializeApp:react-native-firebase/packages/app/lib/internal/web/RNFBAppModule.js
Lines 64 to 66 in b39f5a4
That should be it. If initializeApp is called early enough in bootstrap - prior to an auth instance being configured, then it will look for an authDomain for it's appName in the map as it is instantiated and things will be hooked up.
yuvalhermelin-fijoya commentedon May 20, 2025
Hi @mikehardy - thank you!
What is the status on this if I may ask? Is there already a way to use a custom auth domain with react-native? Thanks!
mikehardy commentedon Jul 1, 2025
No progress as of yet - needs a PR
nyo commentedon Jan 29, 2026
Hi @mikehardy do you plan to work on this someday? Or are you waiting for someone to submit a PR?
mikehardy commentedon Jan 29, 2026
This is something I would like to see supported, and it's a feature gap with native SDKs and firebase-js-sdk so it's labeled in such a way that it will not be stale-closed
However, it's competing with a lot of other priorities here so it never seems to get priority itself. We won't close it, we'd like to fix it, but it's not likely in the short term
The fastest way to see something fixed is always to submit a PR if possible, and we'll do our best - PRs always get more priority than issues-with-no-PRs since PRs are typically much further along in getting something fixed. We collaborate to get those merged with whatever time available before heading into the issues list