Error 403: restricted_client This app is not yet configured to make OAuth requests. To do that, set up the app’s OAuth consent screen in the Google Cloud Console.

[amrhmetwaly]

When Trying to authenticate via the Google Sign In in the pop-up Window I get the following Error

Error 403: restricted_client
This app is not yet configured to make OAuth requests. To do that, set up the app’s OAuth consent screen in the Google Cloud Console.

In the console.developers.google.com I see that the Server Key + Browser Key are all automatically created by Firebase + OAuth 2.0 Web client ID

The Browser API Key matches my firebase configuration API_key

I don't understand what am I missing. If someone can please post the steps that'd be of great help. I'm posting after a couple of hours of looking around.

[bojeil-google]

Hey @zomzom96, additional manual steps may be required in the Google Cloud Console to configure your Google OAuth client. Follow the steps in the Google Cloud Console.

[martypdx]

Two things for those trying to "quick start" and getting running in development:

1. On the displayed 403 Error page, clicking "Learn More" takes you to the GCP "OAuth Consent Screen"
2. There are a lot of fields and no clear instructions about what you need to do For me, the missing piece for me was the support email. Once I added this to the OAuth Consent Screen and clicked Save, things started working in development

[Gabryk]

Two things for those trying to "quick start" and getting running in development:

1. On the displayed 403 Error page, clicking "Learn More" takes you to the GCP "OAuth Consent Screen"
2. There are a lot of fields and no clear instructions about what you need to do For me, the missing piece for me was the support email. Once I added this to the OAuth Consent Screen and clicked Save, things started working in development

I add the logo and the email for assistance, save it and it work just fine.

[abhinavece]

Two things for those trying to "quick start" and getting running in development:

1. On the displayed 403 Error page, clicking "Learn More" takes you to the GCP "OAuth Consent Screen"
2. There are a lot of fields and no clear instructions about what you need to do For me, the missing piece for me was the support email. Once I added this to the OAuth Consent Screen and clicked Save, things started working in development

This helped me too. Added support email and worked like charm !!!

[Marlona]

Two things for those trying to "quick start" and getting running in development:

1. On the displayed 403 Error page, clicking "Learn More" takes you to the GCP "OAuth Consent Screen"
2. There are a lot of fields and no clear instructions about what you need to do For me, the missing piece for me was the support email. Once I added this to the OAuth Consent Screen and clicked Save, things started working in development

I add the logo and the email for assistance, save it and it work just fine.

Same! The email was already there. Added logo and it worked.

[GodwinStanislaus]

2. here are a lot of fields and no clear instructions about what you need to do For me, the missing piece for me was the support email. Once I added this to the OAuth Consent Screen and clicked Save, things started working in development

support email was already there. added a logo and it started working.

[nabilHaouam]

Two things for those trying to "quick start" and getting running in development:

1. On the displayed 403 Error page, clicking "Learn More" takes you to the GCP "OAuth Consent Screen"
2. There are a lot of fields and no clear instructions about what you need to do For me, the missing piece for me was the support email. Once I added this to the OAuth Consent Screen and clicked Save, things started working in development
   Thank you it was the support email for me too , i wouldn't have thought about if i haven't read your comment