API Manager API User Consent Screen Configuration

I created a new project in the Google Developers Console and wanted to add OAuth 2.0 client ID credentials for a web application that needs to set the product name on the consent screen. As soon as I click save after entering the product name on the configuration tab of the OAuth const configuration screen, an error will occur and my changes will not be applied:

Invalid user request. Check the URL and try again.

Server response:

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

I think the problem is with the name or mail, since all parameters except the domain name and support mailing address are optional. Requests all line types as the product name (no spaces, lowercase, long, short, random).

Since the error code is not mail related, I am tempted to believe that my problem is not related to the others that I found .

Also tried to populate each optional parameter with valid URLs, but that didn't help either.

Hope someone ran into a similar problem and can give me some advice. Thanks!

+5
source share
5 answers

So, here is how I fixed it. Go into the adventure story in the picture to fix this little annoying Google-based fiction.

I also created my account long ago as @googlemail.com , but only @gmail.com shown in the drop-down list:

existential crisis, I exist, but in the wrong format

I tried @Peer and added myself to the project again with my full email address @googlemail.com . I did this through this URL:

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

(I am including the link because I did not find a way to go to this from the Google console to clear too clean for real links)

However, even after accepting the invitation, only my @gmail email appeared in the drop-down list on the consent configuration screen, @googlemail.com was still considered "Waiting for a reply" and, most importantly, it still did not remain:

Hello? Can I let me in, please?

Bummer

So, I did the following:

  • Fiddler Opened
  • Click the save button in the consent form to enjoy the error for the last time (and also write it to Fiddler).
  • Find the failed request in Fiddler (beautiful and red for us): One of you is an impostor, and I decided to find out
  • Enable editing on the wrong request: pass the scalpel
  • Go to the Inspectors tab and edit the supportEmail field to change your email address to @googlemail.com : there I fixed it
  • Right click on the wrong request, now it has been edited and go to Replay -> Reissue Requests : Run, Forest, run!

The new request worked in charm, and now that I reloaded my consent screen, the settings were saved, but even better the drop-down value was the full @googlemail.com option:

I finally found myself

So, I selected @googlemail.com and the save button worked successfully after:

Google, please give more coffee to your coders to avoid such gloomy mistakes. Or alcohol. And so the Irish invented Irish coffee, only the Irish can get drunk and sober up at the same time

(Although, apparently, I'm still waiting for my answer ...)

I am not me

+3
source

I fixed the problem by switching the address "@ googlemail.com" to "@ gmail.com" using the 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 Developer Console disappeared.

+2
source

Or with curl and Chrome instead of Fiddler:

  • register your network traffic in Chrome (more tools - developer tools - network)
  • try saving the OAuth confirmation screen again (on the same tab)
  • search for POST request with incorrect Email support ( xyz@gmail.com )
  • use the context menu in the POST request entry in the list and select "Copy as cURL"
  • paste into the terminal and change supportEmail (to xyz@googlemail.com )

At least it worked for me.

+2
source

My email address was a problem. I already created a xxx@googlemail.com account long ago and could only select the xxx@gmail.com. version xxx@gmail.com. Support asked me to add a second account to the project with a different email address. Set up a consent screen and worked like a charm.

0
source

My URI was a problem. But he still gave the same 400 error on top. I had an underscore, but it was an internal DNS that performs routing, so it didn't care. Google did.

eg.

test_underscore.something.com #didn't work being added (it didn't exist) test-hyphen.something.com` did work (it didn't exist)

0
source

Source: https://habr.com/ru/post/1235795/


All Articles