Ataccama ONE Agentic ONE Desktop ONE DQ&C ONE MDM ONE RDM ONE Runtime Server
Downloads

Palantir Foundry Connection

This article describes how to connect to Palantir Foundry using the Palantir Foundry connector and your own JDBC driver.

While Ataccama ONE provides native support for Palantir Foundry, Ataccama cannot redistribute the JDBC driver due to Palantir’s licensing terms. Instead, similarly to the Generic connector, you package, publish, and deploy the driver yourself.

Availability

Data processing & catalog Edge processing Lineage Exceptions

✔

✔

✗

Edge processing: Required. The Palantir Foundry connector is available only on connections processed by an edge instance.

Data transformation plans: Read-only. Writing data back to Foundry is not currently supported.

Prerequisites

  • Review how sources and connections work.

  • Create a source to add this connection to.

  • Register an edge instance on version 2026.08.12.0 or later in your environment. See Edge Processing. Earlier versions do not include the Palantir Foundry connector.

  • Obtain the Foundry JDBC driver from Palantir and make sure your license permits this use.

  • Set up a Foundry OAuth 2.0 client (client ID and client secret) with access to the catalog you want to connect to.

  • Prepare an OCI-compliant container registry that the edge instance can reach, with permission to push artifacts to it.

  • Install the ORAS CLI version 1.2 or later on the machine you publish the driver from.

Package the Palantir Foundry driver bundle

Package, publish, and deploy the driver as described in the Generic connector documentation, starting from Package the driver bundle.

The driver bundle for Palantir Foundry needs only a placeholder .properties file: the driver class, SQL dialect, and query behavior are built into the connector. A single comment line is sufficient, and the file doesn’t need to follow the <name>.properties naming or the ataccama.one.driver.<name>. key prefix that the Generic connector requires.

On edge instances that restrict driver deployment to an allowed repository prefix, publish the Foundry bundle under the native-connector prefix (default byod, bring your own driver) and set the Artifact URL to match. The pull permissions are scoped to the Amazon ECR of the edge instance’s own AWS account and region; a repository in another account or region cannot be used. For details, see Publish under the allowed repository prefix. To change the prefix on a self-managed edge instance, see Customize the driver registry prefixes.

Set up the Palantir Foundry connection

Once you publish the driver to the registry, add a new connection using the following values:

If the catalog path can’t be provided in the connection string (for example, because it contains an ampersand), you also need to add a Catalog driver property. See Catalog paths that contain an ampersand.

Once the deployment status updates to Driver deployed successfully, add credentials before you save the connection.

JDBC connection string format

jdbc:foundrysql://<host>?Catalog=<catalog_path>

Replace the following:

  • <host>: Your Foundry tenant hostname (for example, acme.foundry.com).

  • <catalog_path>: The path to the Foundry catalog you want to connect to (for example, /MyOrg/MyProject). In Foundry, this path is typically referred to as a project path.

Catalog paths that contain an ampersand

A catalog path that contains an ampersand (&), for example /Acme&Co/analytics, can’t be used in the connection string as it can’t be correctly parsed or escaped:

  • If you use a raw ampersand: The connection fails with Invalid connection parameters syntax.

  • If you use an escaped ampersand as %26: The connection test succeeds but browsing the connection fails afterwards. This happens because the connection only reads the catalog once you start browsing.

To resolve this:

  1. Set the path using the Catalog driver property instead:

    • Property name: Catalog

    • Value: Use the project path exactly as it appears in Foundry, including the ampersand.

      For instructions about how to define a driver property, see Add driver properties.

  2. Remove the Catalog parameter from the connection string. If Catalog stays in the connection string, it takes precedence and the driver property is ignored.

    jdbc:foundrysql://<host>

Add credentials

Palantir Foundry uses OAuth 2.0 client credentials (machine-to-machine) authentication. In ONE, you provide the OAuth 2.0 client ID and client secret as the username and password.

Always use the dedicated credential fields for authentication details such as passwords, secrets, and tokens. This ensures credentials are handled with the appropriate level of protection and reliably preserved across environments.

To keep credentials in your existing infrastructure and have ONE retrieve them at runtime, configure a secret management service instead. See Secret Management Service.

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.

  1. Select Add Credentials.

  2. Fill in the following:

    • Name: A name for this set of credentials.

    • Description (Optional): A description for this set of credentials.

    • Username: Your Foundry OAuth 2.0 client ID.

    • Password: Your Foundry OAuth 2.0 client secret.

  3. To use this set of credentials by default when connecting to the data source, select Assign as default.

Next steps

Test and save your connection to complete setup.

If the connection test fails even though the driver deployed successfully, see Troubleshooting the Generic connector. If the connection test passes but browsing the connection fails, check the catalog path: see Catalog paths that contain an ampersand.

Was this page useful?