Using Legacy token, how can I access firebase storage. (Rules should not be public)

[mrgreen007]

Hey,
I'm using legacy token for authentication. And want to use OTA feature through firebase storage. Storage security rules should not be set to public. How should I proceed to achieve this goal? I'm not able to use other auth method due to low ram. If I use other auth like email-pass auth, running good in first one hr. after that I was facing problem like "Memory allocation failed" when token generation method restarted (maybe due to ram <100KB).

If anyone can help, please do. Thanks.

[mobizt]

The legacy token is database secret for RTDB only.

You should debug your code for free Heap and try to reduce the usage.

The database secret is not used for authentication unless the privilege's access to RTDB database by bypassing the authentication.

[mrgreen007]

The legacy token is database secret for RTDB only.

You should debug your code for free Heap and try to reduce the usage.

The database secret is not used for authentication unless the privilege's access to RTDB database by bypassing the authentication.

Thanks!
Do all other auth methods need token regeneration in a particular time interval? Or there is any way to skip token regeneration in periodic interval?

[mobizt]

The auth token issued from googleapis server by sending the request with additional credentials.

You should have enough memory for SSL client to work for sending the request.

If your device free memory is low below 80k, you can't even connect to any secure server using httpclient or WiFiClientSecure.

[mobizt]

You should solve your memory issue instead of asking something like this

[mobizt]

The auth token is short-live token which expired in 1 hour.

The library manage this token included refreshing it when the expiry time is nearly over.

To stop library to process this token, just remove or skip Firebase.ready() and all Firebase functions from your code.

[mrgreen007]

The auth token issued from googleapis server by sending the request with additional credentials.

You should have enough memory for SSL client to work for sending the request.

If your device free memory is low below 80k, you can't even connect to any secure server using httpclient or WiFiClientSecure.

Ok. Got it. Thank you!