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

drive init generates link that returns Error 400: invalid_request #1146

Open
AJPoulter opened this issue Feb 18, 2023 · 12 comments
Open

drive init generates link that returns Error 400: invalid_request #1146

AJPoulter opened this issue Feb 18, 2023 · 12 comments

Comments

@AJPoulter
Copy link

AJPoulter commented Feb 18, 2023

executing drive init generates a url for https://accounts.google.com/o/oauth2/auth?.. that, when used, returns 400, invalid request. Further error message: You can’t sign in because drive for Google Drive sent an invalid request....third party app is using an unsupported OAuth method.
Using the alternative service account option (referencing the generated json credential) does work but the drive resources that can be accessed with the service account are not those of the user account for which the service account should act as a delegate, even though the service account is added to a project with google drive api enabled and has a Google Workspace Marketplace-compatible OAuth client associated with it.

  • Note: setting the Subject in the generated credentials.json to the private user gmail account results in:

Response: { "error": "unauthorized_client", "error_description": "Client is unauthorized to retrieve access tokens using this method, or client not authorized for any of the scopes requested." }

@yanyang1024
Copy link

meet the same problem,anyone can help?

@hightowe
Copy link

hightowe commented Mar 5, 2023

@yanyang1024 - I suggest that you transition to rclone.

@nickgreenway
Copy link

Same issue here.

@leleogere
Copy link

Same issue

@mxvin
Copy link

mxvin commented Apr 10, 2023

consider this repo looks like not being actively maintained, transition to alternative seems more viable for general user.
Sounds like an some changes been done on google side, maybe some enforcement/changes of roles/scope of Oauth, also maybe need to request and change the official api key.
I believe this bug is not that hard to resolve, a pr is very welcome obviously

@mxvin
Copy link

mxvin commented Apr 10, 2023

Maybe its #1142 ???

@jiraff537
Copy link

i try install this
https://packages.gentoo.org/packages/net-misc/drive

and do "drive init" in command line and have this error:

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

***@gmail.com
You can’t sign in because drive for Google Drive sent an invalid request. You can try again later, or contact the developer about this issue. Learn more about this error
If you are a developer of drive for Google Drive, see error details.
Error 400: invalid_request

@VehementHam
Copy link

I have the same issue.

@gmordele
Copy link

gmordele commented Jul 8, 2023

Same issue here

@HRezaei
Copy link

HRezaei commented Jul 10, 2023

same!

@dgonzalez211
Copy link

sam here!

@TheFibonacciEffect
Copy link

The error details are:

Error 400: invalid_request

The out-of-band (OOB) flow has been blocked in order to keep users secure. Follow the Out-of-Band (OOB) flow migration guide linked in the developer docs below to migrate your app to an alternative method.
Request details: redirect_uri=urn:ietf:wg:oauth:2.0:oob

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