# Google Data Catalog

<!-- BEGIN GENERATED:intro -->

The Google Data Catalog connector is a [Palantir-provided driver](../../data-integration/foundry-provided-drivers/index.md) for Google Data Catalog.

To create a new Google Data Catalog source, follow the [standard setup flow for Palantir-provided drivers](../../data-integration/foundry-provided-drivers/index.md#setup), then use the sections below for Google Data Catalog-specific configuration and networking. For the complete property reference, see the [official Google Data Catalog driver documentation ↗](https://cdn.cdata.com/help/HGK/jdbc/pg_connectionj.htm).

<!-- END GENERATED:intro -->

<!-- BEGIN GENERATED:capabilities -->

## Supported capabilities

| Capability | Status |
|---|---|
| Exploration | 🟢 Generally available |
| Batch syncs | 🟢 Generally available |
| Incremental | 🟢 Generally available |
| [OAuth 2.0 authentication](#oauth-20-authentication) | 🟢 Generally available |

<!-- END GENERATED:capabilities -->

<!-- BEGIN GENERATED:configuration -->

## Configuration

The properties below are mandatory or recommended.

| Property | Required? | Description | Default |
|---|---|---|---|
| [`OrganizationId` ↗](https://cdn.cdata.com/help/HGK/jdbc/RSBGoogleDataCatalog_p_OrganizationId.htm) | Mandatory | The ID associated with the Google Cloud Platform organization resource to connect to. | — |
| [`ProjectId` ↗](https://cdn.cdata.com/help/HGK/jdbc/RSBGoogleDataCatalog_p_ProjectId.htm) | Mandatory | The ID associated with the Google Cloud Platform project resource you would like to connect to. | — |
| [`AuthScheme` ↗](https://cdn.cdata.com/help/HGK/jdbc/RSBGoogleDataCatalog_p_AuthScheme.htm) | Recommended | The type of authentication to use when connecting to Google Data Catalog. | `OAuthJWT` |
| [`InitiateOAuth` ↗](https://cdn.cdata.com/help/HGK/jdbc/RSBGoogleDataCatalog_p_InitiateOAuth.htm) | Recommended | Specifies the process for obtaining or refreshing the OAuth access token, which maintains user access while an authenticated, authorized user is working. | `GETANDREFRESH` |
| [`OAuthClientId` ↗](https://cdn.cdata.com/help/HGK/jdbc/RSBGoogleDataCatalog_p_OAuthClientId.htm) | Recommended | Specifies the client Id that was assigned when the custom OAuth application was created. (Also known as the consumer key.) This ID registers the custom application with the OAuth authorization server. | — |
| [`OAuthClientSecret` ↗](https://cdn.cdata.com/help/HGK/jdbc/RSBGoogleDataCatalog_p_OAuthClientSecret.htm) | Recommended | Specifies the client secret that was assigned when the custom OAuth application was created. (Also known as the consumer secret). This secret registers the custom application with the OAuth authorization server. | — |
| [`OAuthJWTCert` ↗](https://cdn.cdata.com/help/HGK/jdbc/RSBGoogleDataCatalog_p_OAuthJWTCert.htm) | Recommended | The JWT Certificate store. | — |
| [`OAuthJWTCertType` ↗](https://cdn.cdata.com/help/HGK/jdbc/RSBGoogleDataCatalog_p_OAuthJWTCertType.htm) | Recommended | The type of key store containing the JWT Certificate. | `GOOGLEJSONBLOB` |
| [`OAuthJWTSubject` ↗](https://cdn.cdata.com/help/HGK/jdbc/RSBGoogleDataCatalog_p_OAuthJWTSubject.htm) | Recommended | The user subject for which the application is requesting delegated access. | — |

<!-- END GENERATED:configuration -->

<!-- BEGIN GENERATED:networking -->

## Networking

The table below lists the domains that the source must be able to access to run.

For each domain, add a corresponding [egress policy](../../administration/configure-egress/index.md). If the source is hosted on-premises and not directly reachable from Foundry, use an [agent proxy egress policy](../../administration/configure-egress/index.md#agent-proxy-egress-policies) instead. The agent host itself must also be able to reach the listed domains. See [using an agent as a proxy](../../data-connection/agent-proxy/index.md) for details.

| Domain  | Required |
|--- |--- |
| accounts.google.com | Always. Required for OAuth |
| googleapis.com | Always |
| datacatalog.googleapis.com | Always |

<!-- END GENERATED:networking -->

<!-- BEGIN GENERATED:oauth -->

## OAuth 2.0 authentication

This connector supports OAuth 2.0 authentication. Follow the [OAuth 2.0 guidance for Palantir-provided drivers](../../data-integration/foundry-provided-drivers/index.md#oauth-20-authentication) to configure and authorize the connection.

<!-- END GENERATED:oauth -->