Can't run grow preprocess because of Google auth problems

[jkevingutierrez]

Lately we haven't been able to run grow preprocess because we are not able to authenticate in Google.

Not sure if something changed in Google's authentication method, but this is the error that we are getting:

Looks like it is something related to

https://developers.google.com/identity/protocols/oauth2/resources/loopback-migration#what-is-the-loopback-ip-address-flow

https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html#dates-loopback

[jeremydw]

Hi Kevin,

When running either the staging or preprocess commands, please supply the --interactive-auth flag to indicate that Grow should receive the Oauth authorization code via a local web server:
https://developers.google.com/identity/protocols/oauth2/native-app#handlingresponse

Here's a sample command (note you can replace "stage" with "preprocess" below).

grow --auth=[[email protected]](mailto:[email protected]) --interactive-auth stage

Note that you'll only need to supply these flags once (when you first authenticate). After that, you can run:

grow stage

Additionally, if you want to reset the local storage of all credentials, you can use:

grow --clear-auth --interactive-auth stage

And that will allow you to start from scratch.

The key requirement here is to supply --interactive-auth which triggers the redirect-based flow (rather than the copy-paste-based flow). As an alternative, you can also authenticate with a service account key file using:

grow --auth-key-file=path/to/key/file.json stage

I'll look into removing the OOB/copy-paste flow from Grow to make this more obvious now that that flow has been deprecated by Google.

Hope that helps,
Jeremy