OOB OAuth deprecation: migrate to OAuth loopback mechanism #1140

Activity

1. tom-ch1 commented on Sep 4, 2022

   

   tom-ch1

   on Sep 4, 2022

   More actions

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

   added a commit that references this issue on Oct 11, 2022

   Replace OOB with loopback 3LO flow

   ...

   This issue will close once commit 85754d4 is merged into the 'master' branch.

   85754d4
3. bsidhom

   added a commit that references this issue on Oct 19, 2022

   Replace OOB with loopback 3LO flow

   ...

   This issue will close once commit 7fefdbd is merged into the 'master' branch.

   7fefdbd
4. jeffman commented on Oct 21, 2022

   

   jeffman

   on Oct 21, 2022

   More actions

   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?

   👍React with 👍3Reacted by teodoryantcheff, Farzan Hajian and Eliot CHRISTON

   👀React with 👀1Reacted by Adam Patterson
5. indev29 commented on Oct 21, 2022

   

   indev29

   on Oct 21, 2022

   Last edited by indev29

   More actions

   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.
6. grovera-md commented on Nov 11, 2022

   

   grovera-md

   on Nov 11, 2022

   Last edited by grovera-md

   More actions

   Is there any update on this issue? Installing the @latest version still produces the error.
7. bsidhom commented on Nov 19, 2022

   

   bsidhom

   on Nov 19, 2022

   Author

   More actions

   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.
8. gmordele commented on Aug 16, 2026

   

   gmordele

   on Aug 16, 2026

   More actions

   I’ve been using "drive" for several years, and I still use it very frequently today.

   What I really appreciate about this project is its simplicity. It does exactly what I need without unnecessary complexity, and over the years it has become a very useful part of my workflow.

   Unfortunately, because of the changes and restrictions introduced by Google, I can now only get it to work properly with one of my Google Drive accounts. For my other accounts, the authentication limitations have made it almost unusable.

   That is quite frustrating, especially because I still find "drive" extremely useful and I have not found another tool that I enjoy using as much for this purpose.

   I understand that maintaining an open-source project takes a lot of time and effort, and I don’t want this message to sound like a demand. I mainly wanted to say that there are still users who rely on this project and genuinely appreciate it.

   If there is any possibility of resuming development, especially to update the authentication process and make it compatible with Google’s current OAuth restrictions, I would be very happy to see this project become fully usable again.

   Thank you for creating and maintaining "drive" over the years. I have personally gotten a lot of value from it, and I would love to continue using it for many more years.

   👍React with 👍1Reacted by Ophir Lifshitz