Firebase 3.0.0 -- anybody know if we're able to get a dedicated IP now?

[Ben Mueller]

We adore Firebase, but are unable to use it in some of our corporate environments due to security concerns. If we were able to have a Firebase instance that sat behind a dedicated IP, then we might be able to get it whitelisted, and happy dances would ensue. Anybody know for certain whether this is/is not possible?

[Mike Mcdonald]

Hey Ben,

Glad you like it :) I assume you're talking about the Firebase Realtime Database?  Unfortunately, we still don't support a fixed IP on a Realtime Database instance, as much of the underlying infrastructure for the Database is the same (though running on Google).

Is there a reason that you can't whitelist *.firebaseio.com (or <your-namespace>.firebaseio.com) instead of using the IP?

Thanks,

--Mike

[Ben Mueller]

That is, apparently, not an option. I'll triple-check, but the people who tell me that IPs are not an option are familiar enough with Firebase to know that data flows to and from a single domain, and that this is not secure enough for our corporate needs. Had I to hazard a guess, it would be that IPs can change underneath a domain, and this poses enough of a security concern in some cases that it's a non-starter.

Are fixed IPs on the horizon at all?

[Steffen Frost]

Not an expert on networking, but how would you use a browser at work if the IPs can change underneath a domain, like say google.com or gmail.com?

-s

[Ben Mueller]

I'm not an expert either. My understanding is that in the corporate environments where we'd like access to Firebase, those machines cannot access sites which are not whitelisted, which means sites like google.com and so forth are *not* accessible. To be clear, I'm 99.9% sure that the people telling me we need fixed IPs in order for this to work are not mistaken. If Firebase doesn't offer that service at this point, that's fine.

[Kato Richardson]

This isn't really compatible with Firebase infrastructure, where servers can spin up or down at any time, and where your app can move between servers without notice to meet the demands of massive scaling realtime usage.

We don't have any plans to offer static ips, sorry. A more likely resolution here would be some sort of proxy support, which could definitely be on the horizon if we can put together some sort of functional plan of how that would work.

Ideas and use cases certainly appreciated!

☼, Kato

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/3f14feee-2ca5-49ca-9846-d7c45dae0312%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Kato Richardson |

Developer Programs Eng |

kato...@google.com |

775-235-8398

[Clement Wehrung]

Hey Kato / Firebase team, 

Any update on this thread? We're facing the same issue here with enterprise customers who cannot whitelist wildcards. I'm happy to collect more relevant info if it can help. 

Thanks!

[Mike Mcdonald]

Clement,

Unfortunately no additional info on this. Firebase features still run on shared infrastructure, and we can't guarantee particular developers (or end users) particular IPs.

Thanks,

--Mike

[Clement Wehrung]

Mike - Thanks for the update. Does this also apply to the subdomain? (in our case, it's more about having a constant subdomain.firebaseio.com than the IP). 

--
You received this message because you are subscribed to a topic in the Google Groups "Firebase Google Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/firebase-talk/SlCsde0zxQM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to firebase-tal...@googlegroups.com.

To post to this group, send email to fireba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/75288e49-0c0d-480f-b61b-174409bdc217%40googlegroups.com.

[Mike Mcdonald]

I'm not sure if I understand the question: is it "does my database instance stay on the same 'foo.firebaseio.com' domain?" or is it "does that domain have the same IP?"

If it's the former, yes, we don't change the name of your database; if it's the latter, the answer is maybe but subject to change, since it could shift around.

Thanks,

--Mike

[Clement Wehrung]

Sorry Mike, let me rephrase that: would the service the clients connect to behind the scenes s-usc1c-nss-122.firebaseio.com be constant for a database "projectXYZ.firebaseio.com" or is this subject to change as well? 

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/baf1a6eb-298e-452d-a27e-b9cb0dedde75%40googlegroups.com.

[Jacob Wenger]

It is subject to change. You can be moved to a different server (the nss-### part of that URL) at any point and shouldn't rely on that for anything.

Cheers,
Jacob

To unsubscribe from this group and all its topics, send an email to firebase-talk+unsubscribe@googlegroups.com.

To post to this group, send email to fireba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/baf1a6eb-298e-452d-a27e-b9cb0dedde75%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to firebase-talk+unsubscribe@googlegroups.com.

To post to this group, send email to fireba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/CAJe6AKmxd124hvwdbo29%2Bt532mRhyr57xVjpibmEO%2BZK7%3De6iw%40mail.gmail.com.