Use your own OAuth client ID

When you sign in to an OAuth service such as Google Drive, the service sees an app asking for access, identified by a client ID. Unless you say otherwise, CloudMount uses rclone’s built-in client IDs, which are shared by every rclone user in the world.

Why use your own

• Google is retiring rclone’s shared client ID. rclone’s documentation says the shared Google Drive client ID stops working during 2026, and recommends that everyone create their own. Drives that use it will need a new sign-in with your own client ID.
• Rate limits are shared. Services limit how many requests each client ID may make. With a shared ID, everyone’s traffic counts together, which can make your drive slow or show rate limit errors at busy times. Your own ID has its own quota.
• Some organisations block unknown apps. A work or school account may only allow apps its administrator approved.

How

1. Create a client ID and secret in the service’s developer console. rclone’s documentation has step-by-step guides:

   • Google Drive: Making your own client_id
   • OneDrive: Getting your own Client ID and Key
   • Dropbox: Get your own Dropbox App ID
   • Box: Get your own Box App ID
   • Others: create an app in the service’s developer console.

   Where a guide asks for a redirect URL, use http://localhost:53682/ (or http://127.0.0.1:53682/ where the service needs an IP address). CloudMount signs in through rclone on your device at that address.

2. In CloudMount, add the drive (or edit it) and fill in client_id and client_secret. When adding a drive, they’re under Advanced options.

3. Sign in. For an existing drive, use Reconnect (Android) or Sign in again (Windows) so the new client ID takes effect.

Google: publish the app

For Google Drive, keep the OAuth consent screen’s audience as External and, once it works, choose Publish app. While it’s in Testing, Google expires your sign-in after seven days.