Skip to main content
Skip table of contents

Google Cloud API Integration for OAuth 2.0

Overview

You can integrate OAuth 2.0 authentication for BigQuery connections by registering the Client ID and Client Secret generated from your Google Cloud API. For instructions on setting up OAuth 2.0 in the Google Cloud API console, please refer to the relevant Google Cloud documentation.

Googl Cloud API Integration

image-20250116-090507.png

Google Cloud API Integration for OAuth 2.0

Adding an OAuth 2.0 Client ID

  1. Navigate to the General > System > Integration menu.

  2. Under the Authentication section, click the Google Cloud API tile.

  3. In the OAuth 2.0 Client IDs section, click the +Add button.

    image-20250116-102818.png

    Add Client ID

  4. Enter the following information in the pop-up window and click the Save button:

    image-20250116-103102.png

    Enter information for each input field of OAuth 2.0 Client ID

    • Name: Enter a name that is easy to identify in the list.

    • Client ID: Enter the Client ID obtained from the Google API Console.

    • Client Secret: Enter the Client Secret obtained from the Google API Console.

Editing an OAuth 2.0 Client ID

  1. From the list, click the specific Client ID row you wish to edit.

  2. Modify the information in the pop-up window and click the Save button.

Deleting an OAuth 2.0 Client ID

  1. From the list, check the box next to the specific Client ID you wish to delete.

    image-20250116-110050.png

    Delete Client ID

  2. Click the Delete button located at the top of the list.
    If the Client ID you are trying to delete is currently linked to a connection setting, a warning message will be displayed, and you will not be able to delete it. You must first remove the OAuth configuration from the connection settings or delete the connection itself.

    image-20250116-105240.png

    Notice when attempt to delete Client ID in use

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.