Google Drive Connection
This article describes how to connect to Google Drive.
Availability
| Data processing & catalog | Edge processing | Lineage | Exceptions |
|---|---|---|---|
✔ |
✗ |
✗ |
|
Prerequisites
-
Review how sources and connections work.
-
Create a source to add this connection to.
-
Configure a Google Cloud application with OAuth 2.0 authentication. See Google Cloud Application Configuration.
Add a connection
-
Go to [your source] > Connections and select Add Connection.
-
In Connection type, select Google Drive.
-
Fill in the following:
-
Name: A meaningful name for your connection. Used to indicate the location of catalog items.
-
Description (Optional): A short description of the connection.
-
Add credentials
| Only OAuth 2.0 authentication is supported. |
-
Select Add Credentials.
-
Fill in the following:
-
Name: Provide a clear name for this set of credentials.
-
Description (Optional): Explain what the credentials are used for or provide other useful information.
-
Redirect URL: This field is predefined and read-only. This URL is required to receive the refresh token.
-
Client ID: The OAuth 2.0 client ID from your Google Cloud application.
-
Client secret: The OAuth 2.0 client secret from your Google Cloud application.
If the client secret is lost or compromised, you can generate a new one in the Google Cloud Console under APIs & Services > Credentials. -
Authorization Endpoint: The OAuth 2.0 authorization endpoint.
The default value is
https://accounts.google.com/o/oauth2/v2/auth. -
Token Endpoint: The OAuth 2.0 token endpoint.
The default value is
https://oauth2.googleapis.com/token.
-
-
In Refresh token, select Generate to create a new token.
This opens a Google sign-in screen. Select the Google account you want to use for this connection and allow access. Once generated, the token’s expiration date is shown in Refresh token valid till.
-
To use this set of credentials by default when connecting to the data source, select Set as default.
| One set of credentials must be defined as default for each connection. Otherwise, DQ evaluation fails and previewing data in the catalog is not possible. |
Add write credentials
If you want to export data to this source, add write credentials. Select Add Credentials and follow the instructions in Add credentials.
Troubleshooting
Connection test fails
Check the inputs carefully, especially the Client ID and Client secret fields for extra spaces.
If this doesn’t help, verify that the redirect URI of ONE is listed in the authorized redirect URIs of your Google Cloud application. For details, see Google Cloud Application Configuration.
Refresh token generation fails
If a refresh token was previously issued but is now lost (for example, the connection was deleted or the field was overwritten), generating a new token can fail because Google has already issued one.
To resolve this, go to Google Account Permissions and remove access for the Google Cloud application, then try generating the token again.
Was this page useful?