Configure the Google Drive Authorized Redirect URI for QCSB

This article shows how to use the exact redirect URI shown by QCSB in the Google Cloud OAuth configuration and understand why the connection must first be saved so callback state can bind to a real connection.

How to do it

  1. Open or begin creating the Google Drive Storage Connection in QCSB.
  2. Copy the exact read-only Authorized redirect URI shown in the connection form.
  3. Open Google Cloud Console, edit the OAuth 2.0 Web application, and add the copied URI under Authorized redirect URIs.
  4. Save the Google application configuration. Do not remove a fixed query string from the QCSB URI if one is shown.
  5. Return to QCSB, save the Client ID/Secret, and use Connect Google Account to verify the callback returns to the same connection successfully.

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.