Open tunes0710 opened 1 year ago
yeap. same problem i have. is this project outdated???? or broken. is there a fix or workaround?
Same here. Does anyone have a solution?
Same here
Hey guys, I have taken a look at the issue and it does not seem trivial to resolve, if anybody wants to contribute I would gladly help you set it up locally. Added message to README to warn people
I think becasue of this.... big change On February 16 2022
https://developers.google.com/identity/protocols/oauth2/resources/loopback-migration
what do we do now?
Hey everyone, @skupjoe @cheehoong @drchslrk @FrankM77 @tunes0710 I think there is a potential fix, it just involves using grive2 latest version. If anyone wants to try I built a new snapshot. If this works I will publish it as a release.
docker pull agusalex/grive2:snapshot
@agusalex So I am no longer seeing the container crashing and bootlooping over and over. Ie, it successfully halts at Please open this URL in your browser to authenticate Grive2:
.
But I am getting an Error 400: invalid_request
when I go to the URL:
However, this 400 error is now for "loopback flow". Ie, I am no longer seeing The out-of-band (OOB) flow has been blocked in order to keep users secure.
error.
So, this is an improvement, thanks, but it's still not working, unfortunately.
Maybe somebody else here can try?
Side note: It seems that the new "loopback" method of authenticating involves having the grive2 service listen on a random port and then you open the link in your browser and it connects to this temporary webserver. At least that's how it seems.
So, for this to work, the port would need to be open and listening and connected-to from a browser that is all the same host.
I tried switching over to --network host
when running this container and launching this from a host that I have access to a GUI browser, and I confirmed that the random port is listening/accessible, but I still get this error.
I got different error after using ... https://accounts.google.com/o/oauth2/auth/oauthchooseaccount?scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fdrive&redirect_uri=urn%3Aietf%3Awg%3Aoauth%3A2.0%3Aoob&response_type=code&client_id=**FILL_HERE_YOUR_CLIENT_ID** <-- changed to my Client ID
Please remove this from the unraid app store if it's not going to be fixed....
On the setup stage Append your CLIENT_ID and then go to this URL https://accounts.google.com/o/oauth2/auth/oauthchooseaccount?scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fdrive&redirect_uri=urn%3Aietf%3Awg%3Aoauth%3A2.0%3Aoob&response_type=code&client_id= FILL_HERE_YOUR_CLIENT_ID
We can no longer do this due to https://developers.google.com/identity/protocols/oauth2/resources/oob-migration
You can’t sign in because Unraid Gdrive 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 Unraid Gdrive, see error details. Error 400: invalid_request
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