Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Google API Manager OAuth consent screen configuration Error

I've created an new project in the Google Developers Console and wanted to add OAuth 2.0 client ID Credentials for a Web Application, wich requires me to set a product name on the consent screen. Once I hit save after entering a product name on the OAuth constent screen configuration tab an error occurs and my changes are not applied:

The user request is invalid. Please check your URL and try again.

Server Response:

{
  "error": {
    "code": 400,
    "message": "Request contains an invalid argument.",
    "status": "INVALID_ARGUMENT"
  }
}

I guess the problem is name or mail related since all parameters except for poduct name and support mail address are optional. Tries all sort of strings as product name (without space, lowercase, long, short, random).

Since the error code is not mail related I'm tempted to believe that my issue isn't related to others I found.

Also tried to fill every optional parameter with valid URLs, but that did not help either.

Hope someone encountered a similar issue and can give me some advice. Thank you!

like image 937
Peer Weidner Avatar asked Nov 12 '15 15:11

Peer Weidner


2 Answers

So here's how I fixed this. Let's go on a picture adventure story to fix this little pesky Google-total-fudge-up.

I, too, created my account a long while ago as @googlemail.com but in the drop down only @gmail.com was showing:

existential crisis; I exist but in the wrong format

I tried @Peer's answer and added myself to the project again with my full @googlemail.com email. I did this via this URL:

https://console.cloud.google.com/projectselector/permissions/projectpermissions

(I include the link because I found no way to navigate to this from the too-clean-for-actual-links Google Console)

However, even after accepting the invitation, only my @gmail email appeared in the drop down list on the consent configuration screen, the @googlemail.com was still regarded as "Waiting for response" and, best of all, it still didn't save:

Hello? Can I let me in, please?

Bummer

So I did the following:

  • Opened up Fiddler
  • Hit the save button on the consent form to enjoy the error one last time (and also record it in Fiddler)
  • Locate the bad request in Fiddler (nice and red for us): One of you is an imposter and I'm determined to find out
  • Enable editing on the bad request: pass the scalpel
  • Select the Inspectors tab and edit the supportEmail field to change my email address to @googlemail.com: there I fixed it
  • Right click on the bad request now it has been edited and navigate to Replay -> Reissue Requests: Run, Forest, run!

The new request worked a charm, and now when I reloaded my consent screen the settings had saved, but even better the drop down had the full @googlemail.com option:

I finally found myself

So I selected my @googlemail.com address and the save button worked happily ever after:

Google, please give more coffee to your coders to avoid such grim bugs. Or alcohol. Or both. That's why the Irish invented Irish coffee; only the Irish can get drunk and sober up at exactly the same time.

(Although apparently I am still waiting for my own response...)

I am not me

like image 179
joshcomley Avatar answered Oct 31 '22 14:10

joshcomley


I fixed the problem by switching the "@googlemail.com" address to "@gmail.com" via Gmail-settings ( https://mail.google.com/mail/#settings/accounts): Described here: https://support.google.com/mail/answer/159001?hl=en

After the change, the problem in the Google developers console diappeared.

like image 22
fmi Avatar answered Oct 31 '22 13:10

fmi