I just got rclone v1.63.1 and when trying to set up an rclone config (for GOOGLE DRIVE) it keeps taking me to the old auth method which rclone (to my knowledge and use) stopped using since January when google retired it. But for some reason it does it when I do it on a headless machine.
This is the output
Verification code
Go to this URL, authenticate then paste the code here.
https://accounts.google.com/o/oauth2/auth?access_type=offline&client_id=xxxxxxxx.apps.googleusercontent.com&redirect_uri=urn%xxxx
Which threw me off because I thought google updated to oauth3
`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
rclone v1.56.1
- os/version: debian 11.5 (64 bit)
- os/kernel: 5.15.107+truenas (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.16.8
- go/linking: static
- go/tags: none
Command: rclone config - then selecting Google Drive, putting client and secret, selecting headless machine.
A log from the command with the -vv
flag
Am I missing something or is this a bug
?