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.

Sign up for GitHub

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

Jump to bottom

OOB OAuth deprecation: migrate to OAuth loopback mechanism #1140

Open
bsidhom opened this issue Aug 23, 2022 · 5 comments · May be fixed by #1142
Open

OOB OAuth deprecation: migrate to OAuth loopback mechanism #1140

bsidhom opened this issue Aug 23, 2022 · 5 comments · May be fixed by #1142

Comments

@bsidhom
Copy link

bsidhom commented Aug 23, 2022

The Out-of-Band workflow will be deprecated in October 2022. As far as I can tell, drive still uses OOB (copy/paste) to authenticate.

I think that existing (authenticated) clients will continue to work at this point, but I'm not sure how long new authentication flows will continue to work. Desktop applications should migrate to a loopback device flow.
@tom-ch1
Copy link

tom-ch1 commented Sep 4, 2022

Checkout how Brian adapted grive2 to migrate oob to loopback flow: vitalif/grive2#369
Maybe the same approach works here

bsidhom added a commit to bsidhom/drive that referenced this issue Oct 11, 2022
@bsidhom
Replace OOB with loopback 3LO flow
85754d4 
The out-of-band flow is deprecated and can no longer be used to
authorize new clients:
https://developers.google.com/identity/protocols/oauth2/resources/oob-migration#what-is-oob.
Desktop clients should be migrated to the loopback flow:
https://developers.google.com/identity/protocols/oauth2/resources/oob-migration#desktop-client.
Fixes odeke-em#1140.
@bsidhom bsidhom linked a pull request Oct 11, 2022 that will close this issue
Open
bsidhom added a commit to bsidhom/drive that referenced this issue Oct 19, 2022
@bsidhom
Replace OOB with loopback 3LO flow
7fefdbd 
The out-of-band flow is deprecated and can no longer be used to
authorize new clients:
https://developers.google.com/identity/protocols/oauth2/resources/oob-migration#what-is-oob.
Desktop clients should be migrated to the loopback flow:
https://developers.google.com/identity/protocols/oauth2/resources/oob-migration#desktop-client.
Fixes odeke-em#1140.
@jeffman
Copy link

jeffman commented Oct 21, 2022

When I visit the link produced by drive init ~/gdrive, I get:

Access blocked: drive for Google Drive’s request is invalid

You can’t sign in because drive for Google Drive sent an invalid request. You can try again later, or contact the [developer](https://accounts.google.com/) about this issue. [Learn more about this error](https://support.google.com/accounts/answer/12379384)
If you are a developer of drive for Google Drive, see [error details](https://accounts.google.com/).
Error 400: invalid_request

Is the error I'm seeing due to this issue?

@indev29
Copy link

indev29 commented Oct 21, 2022 •
edited
Loading

Is the error I'm seeing due to this issue?

Unfortunately, yes. You can try a fix from #1142 for now.
I'm not sure when it will be merged to master, seems like the project is not actively maintained at the moment.

@grovera-md
Copy link

grovera-md commented Nov 11, 2022 •
edited
Loading

Is there any update on this issue? Installing the @latest version still produces the error.

@bsidhom
Copy link
Author

bsidhom commented Nov 19, 2022

The fix from #1142 hasn't been merged yet, so it won't appear in @latest. I'm not sure if this repo is still maintained, but for now, you'll have to patch in that change and build locally if you want the fix.

@cdanielw cdanielw mentioned this issue Nov 23, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Replace OOB with loopback 3LO flow bsidhom/drive
5 participants
@bsidhom @jeffman @indev29 @tom-ch1 @grovera-md