Google Drive Requirements and OAuth Application Setup

This article shows how to prepare a Max/All Access Google OAuth client, understand per-connection Client ID/Secret use, choose the correct application settings, and keep OAuth credentials isolated to the intended connection.

How to do it

  1. Create or choose a Google Cloud project controlled by the organization that owns the connection.
  2. Enable the Google Drive API and configure the OAuth consent screen for the intended users.
  3. Create an OAuth 2.0 Web application.
  4. Begin a Google Drive Storage Connection in QCSB and copy the exact read-only Authorized redirect URI displayed by QCSB.
  5. Add that exact URI to the Google OAuth application. Do not simplify or reconstruct it manually; the QCSB callback may contain a fixed Joomla query string.
  6. Copy the Google Client ID and Client Secret into the QCSB connection form, save the connection, then authorize the Google account.

Verify the result

  • Test Connection succeeds.
  • The displayed/usable root is exactly the intended root and no parent folder is reachable.
  • A normal authorized user can perform only the operations intended for that connection/Workspace role.

Troubleshooting

  • If the provider is unreachable, test the connection in Administrator before troubleshooting the Workspace UI.
  • Keep passwords, OAuth secrets/tokens, private keys, and unrestricted private paths out of public screenshots and support posts.

Community Discussion

For practical QCSB workflows and discussion with other Joomla site owners, visit the QC Storage Bridge Community. For private support, bug reports, account-specific entitlement issues, or feature requests, use the QuantaCade support system.