Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Grow uses OOB to authenticate, which is outdated #1215

Open
tpeng3 opened this issue Jul 18, 2023 · 2 comments
Open

Grow uses OOB to authenticate, which is outdated #1215

tpeng3 opened this issue Jul 18, 2023 · 2 comments

Comments

@tpeng3
Copy link

tpeng3 commented Jul 18, 2023

Hello, I noticed grow's oauth.py but that's no longer supported by Google as of 2022. It needs to be migrated otherwise there'll be an issue deploying staging links to places like webreview.

https://developers.google.com/identity/protocols/oauth2/resources/oob-migration

@jeremydw
Copy link
Member

Hi there,

This came up earlier on the growsdk mailing list. Here are the instructions I sent over:

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:

grow --auth=[user@domain.com](mailto:user@domain.com) --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.

We can leave this issue open as the tracking issue for removing the flow.

@tpeng3
Copy link
Author

tpeng3 commented Aug 1, 2023

Thank you, the command fixed the issue for me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants