How do I resolve 400 bad request in Google Picker dialog in test application?

[Liam Monninger]

I'm running into trouble with test users and the Picker component in my web applicaton.

My test users, but not myself are receiving a 400: The server cannot process the request because it is malformed when attempting to access the picker. Because I am not receiving the error message, I believe this must have something to do with the IAM.

• I believe I've been able to eliminate managed browsers settings, cookie settings, and extensions as possible sources of error.
• I've also added the users to the GCP project with the Browser role, though they did not receive invites.

What do I need to try next to resolve this issue?

[Liam Monninger]

I made an SO post about this here. I've tried adding users, assigning the organization, etc.

Best,

Liam

[Horace (Cloud Platform Support)]

Hello Liam,

A 400 Bad Request, also known as a 400 error, is perceived by the server as a generic client error and it is returned when the server determines the error doesn’t fall in any of the other status code categories. There are various root causes that can trigger the 400 Bad Request error and, even if this error isn’t specific to any particular browser or OS (operating system), the fixes do vary slightly.

Is the error only to a specific user on a specific machine? Have they tried using another workstation or another browser? Can you kindly ensure that all their extensions are disabled.

Lastly, I see that you opened a case with GCP support and posted on stackoverflow [1], kindly monitor both since support for the Google Picker API [2] is provided by Google Workspace support. Both should be picked up by Workspace support. They should be able to dive further into your case.

Regards

[1] https://stackoverflow.com/questions/70308692/how-do-i-resolve-400-bad-request-in-google-picker-dialog-in-test-application  

[2] https://developers.google.com/picker/docs