Google OAuth migration for rclone

Help and Support
6

Here is what you need to know.

TLDR this will only affect you if you need to reconfigure rclone remotely, if you do use rclone 1.58.

Here are the details

Normal operations

You can carry on using your existing rclone.conf - old versions of rclone will keep working just fine.

Re-authenticate with google locally

If you are making a new config with rclone config, or running rclone config reconnect and answer Y to this question

Use auto config?
 * Say Y if not sure
 * Say N if you are working on a remote or headless machine

y) Yes (default)
n) No
y/n> Y

Then you don't need to do anything. Old versions of rclone will continue to work just fine.

Re-authenticate with google remotely

If you are making a new config with rclone config, or running rclone config reconnect and answer N to this question

Use auto config?
 * Say Y if not sure
 * Say N if you are working on a remote or headless machine

y) Yes (default)
n) No
y/n> N

You'll need to use rclone 1.58 or later and rclone authorize or use any version of rclone and the copying the config method.

You cannot use the copying the token from the web page method any more - that's the OOB method that has been deprecated.

Client IDs

You don't need to recreate your client IDs or reconfigure anything in your Google Console.

3 Likes