Resolving "Redirect URI Mismatch" Error with Google Integration

When integrating Google data sources with Bold BI, you may encounter a “redirect URI mismatch” error. This typically happens when the redirect URI provided in the Google Cloud Console does not match the URI to which Google is sending the response.

Step 1: Verify the Redirect URI in Your Application

First, ensure that the redirect URI in your application is the one you intend to use. This URI is where Google will send the response after a user authorizes your application.

Step 2: Configure the Redirect URI in Google Cloud Console

1. Go to the Google Cloud Console.
2. Select the project associated with your application.
   
   
3. Navigate to the “Credentials” page.
   
   
4. Click on the OAuth 2.0 Client ID that you are using for your application.
5. Under “Authorized redirect URIs,” click “ADD URI” to enter your redirect URI. The base URL for the redirect URL needs to be the Bold BI site URL.

Syntax:

http[s]://{{host:port_number}}/bi/designer/v1.0/oauth/agent

6. Save your changes.

Step 3: Ensure Consistency

• Make sure that the redirect URI in your application code matches exactly with the one you have provided in the Google Cloud Console, including the protocol (http or https), domain, port, and path.
• Additionally, please ensure that you have included the Client ID and Client secret within the Bold BI application. Click on the configure button and proceed with adding this information.
  
  
• You can get the ID and client secret in the additional information when you click into the OAuth 2.0 Client ID.
  
  

Step 4: Test the Integration

• After updating the redirect URI, test the integration by going through the authorization flow again. If the URIs match, the error should no longer appear.

Additional Reference:

• Google Drive Connector
• Google Sheets Connector