The oldest one is from January 2021, another one from December 2021, and one I created today - March 2022. I was able to reproduce the same problem in a dev domain.This is a command line script, so I use the 'copy/paste' verification method as documented here hence the urn:ietf:wg:oauth:2.0:oob redirect URI (copy/paste is the only friendly way to run this on a headless machine which has no browser).Another client id in the same project works and there are no obvious differences between the client IDs - they are both 'Desktop' type which only gives me a Client ID and Client secret that are different.I do have 'Trust internal, domain-owned apps' enabled for the domain.Therefore any mentions of Google review of the project, or publishing status are irrelevant The OAuth consent screen for this project is marked as 'Internal'.How do I get through this error? It is important to note that: If you’re the app developer, make sure that these request details This content has not been reviewed or verified by Google. The content in this section has been provided by the app developer.

You can let the app developer know that this app doesn't comply with OAuth 2.0 policy for keeping apps secure. You can't sign in to this app because it doesn't comply with Google's

Recently, after making another client_id in the same project, I started getting an error message similar to the one described in localhost redirect_uri does not work for Google Oauth2 (results in 400: invalid_request error). We have some apps (or maybe we should call them a handful of scripts) that use Google APIs to facilitate some administrative tasks.

Google drive install error 400