Is there any limits on Firebase Validating Auth Tokens

[RamaKrishna Ponnaluri]

Hi,

We are building a Chatbot App. An Android App for front-end which talks to our Custom API built on NodeJS which in-turn talks to api.ai for NLP.

We are using Firebase SDK at Client side in Android App and Firebase Admin SDK in NodeJS for Authentication.

If I have to secure my api end point then I have to validate each message request, I should be generating idToken asynchronously by currentUser.getToken() and sending it along with the message in headers. On the server side, with the Admin SDK I should be verifying the idToken and then process it further.

This means that I will be hitting Firebase every time I verify the token and will be counted as one connection.

I understand that there is a limitation of 100 simultaneous connections for Spark and 10000 for Flame and Blaze.

This means that I can process 100 messages simultaneously. Simultaneously in the sense that 100 messages per second.

If this limit exceeds I should be upgrading to Flame to scale up.

Please let me know if my understanding is correct or if there is any better way of implementation.

I am totally new to Firebase, NodeJS and Android, coming from an Industrial Automation background so this might be a basic question.

thanks and regards

RamaKrishna

[Jacob Wenger]

Hey there,

The plan you laid out for generating ID tokens on client devices, sending them to your server, and validating them on your server sounds exactly correct. Nice work!

As for ID token verification limits, there are none! The 100 simultaneous connections limit is for the Realtime Database only. ID token verification does not involve the Realtime Database at all. So, you can safely call the Firebase Admin Node.js SDK's verifyIdToken() method as much and as often as you'd like without worrying about getting rate limited in any way.

Cheers,

Jacob

--
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/431757e1-79fd-40d6-a53d-d33dbae302dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[RamaKrishna Ponnaluri]

Thanks Jacob, that's great news for us.

On Friday, February 3, 2017 at 12:47:52 AM UTC+5:30, Jacob Wenger wrote:

Hey there,

The plan you laid out for generating ID tokens on client devices, sending them to your server, and validating them on your server sounds exactly correct. Nice work!

As for ID token verification limits, there are none! The 100 simultaneous connections limit is for the Realtime Database only. ID token verification does not involve the Realtime Database at all. So, you can safely call the Firebase Admin Node.js SDK's verifyIdToken() method as much and as often as you'd like without worrying about getting rate limited in any way.

Cheers,

Jacob

On Thu, Feb 2, 2017 at 3:30 AM, RamaKrishna Ponnaluri <getr...@gmail.com> wrote:

Hi,

We are building a Chatbot App. An Android App for front-end which talks to our Custom API built on NodeJS which in-turn talks to api.ai for NLP.

We are using Firebase SDK at Client side in Android App and Firebase Admin SDK in NodeJS for Authentication.

If I have to secure my api end point then I have to validate each message request, I should be generating idToken asynchronously by currentUser.getToken() and sending it along with the message in headers. On the server side, with the Admin SDK I should be verifying the idToken and then process it further.

This means that I will be hitting Firebase every time I verify the token and will be counted as one connection.

I understand that there is a limitation of 100 simultaneous connections for Spark and 10000 for Flame and Blaze.

This means that I can process 100 messages simultaneously. Simultaneously in the sense that 100 messages per second.

If this limit exceeds I should be upgrading to Flame to scale up.

Please let me know if my understanding is correct or if there is any better way of implementation.

I am totally new to Firebase, NodeJS and Android, coming from an Industrial Automation background so this might be a basic question.

thanks and regards

RamaKrishna

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