Problem with HTTP Cloud Function | 403 Forbidden
1,787 views
Skip to first unread message
Franck-Kevin NANADEMEN
May 6, 2019, 10:02:43 AM5/6/19
to Firebase Google Group
Hello,
We are having some issues with our HTTP Callable Cloud Functions.
We are getting a 403 Forbidden.
The problem occurs whether we deploy with firebase CLI or gcloud CLI. It seems to work only if we use the cloud function "Tester" in GCP console.
Please this is a blocking issue for us !
Can you tell us what we could do to solve it ? Is there maybe an ongoing issue in Cloud Function infrastructure (we don't see any problem on the status.firebase.google.com or status.cloud.google.com pages)
Thank you in advance.
This e-mail transmission (message and any attached files) may contain information that is proprietary, privileged and/or confidential to Veolia Environnement and/or its affiliates and is intended exclusively for the person(s) to whom it is addressed. If you are not the intended recipient, please notify the sender by return e-mail and delete all copies of this e-mail, including all attachments. Unless expressly authorized, any use, disclosure, publication, retransmission or dissemination of this e-mail and/or of its attachments is strictly prohibited.
Ce message electronique et ses fichiers attaches sont strictement confidentiels et peuvent contenir des elements dont Veolia Environnement et/ou l'une de ses entites affiliees sont proprietaires. Ils sont donc destines a l'usage de leurs seuls destinataires. Si vous avez recu ce message par erreur, merci de le retourner a son emetteur et de le detruire ainsi que toutes les pieces attachees. L'utilisation, la divulgation, la publication, la distribution, ou la reproduction non expressement autorisees de ce message et de ses pieces attachees sont interdites.
--------------------------------------------------------------------------------------------
Kato Richardson
May 6, 2019, 6:09:40 PM5/6/19
to Firebase Google Group
I don't think there's enough info here to be helpful. It seems likely that you are not calling the correct callable method name, or that the endpoint is not set up as a callable.
Some corresponding client and server logs, along with sample code of the deployed Functions and the client app might help us to understand.
☼, 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/c8359cde-cbeb-49dd-a38b-8c059c8dbc29%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Luke Gackle
Jun 10, 2020, 8:44:08 AM6/10/20
to Firebase Google Group
I believe Google Cloud Functions deployed some new IAM functionality recently, as such newly created functions don't have the right permissions set for public requests, this might explain your issue.
I realise this thread is old now but incase it's still helpful or helpful for someone else, I've documented how to resolve it on my blog, essentially you have to add allUsers to the function with the cloud function invoker role.
Step by step guide here: https://lukestoolkit.blogspot.com/2020/06/google-cloud-functions-error-forbidden.html
I realise this thread is old now but incase it's still helpful or helpful for someone else, I've documented how to resolve it on my blog, essentially you have to add allUsers to the function with the cloud function invoker role.
Step by step guide here: https://lukestoolkit.blogspot.com/2020/06/google-cloud-functions-error-forbidden.html
Reply all
Reply to author
Forward
0 new messages