Trino JDBC Connection

Connect to Trino via JDBC

For a Data Analyst connecting a BI tool, notebook, or JDBC-compatible client (DBeaver, SQL Workbench, Tableau, etc.) directly to your xDP Trino instance — no XDP UI session required.

Every xDP Trino instance is reachable over a public JDBC gateway endpoint. Instead of a username/password pair tied to a personal login, you authenticate with an API key pair issued from your xDP account:

Username = your Access Key
Password = your Secret Key

The JDBC URL also identifies which Trino instance you're connecting to, since a single gateway endpoint can route to multiple tenants and dataplanes. You do this with two extraCredentials parameters:

tenant — your organization's tenant name in xDP
dataplane — the name of the dataplane (compute cluster) where your Trino instance is installed

Note: Trino's own JDBC driver requires the SSL flag and extraCredentials on every connection — omitting either results in an authentication failure, not a partial connection.

Getting your Access Key and Secret Key

Sign in to the xDP UI.
Go to Settings → Credentials.
Create a new credential (or use an existing one) and copy its Access Key and Secret Key.

Warning: The Secret Key is shown only once at creation time. Store it in a password manager or secrets vault — if lost, you'll need to regenerate a new key pair.

Building your JDBC URL

The connection string follows this structure:

jdbc:trino://<jdbc-gateway-host>:443/<catalog>?SSL=true&extraCredentials=tenant:<your-tenant-name>;dataplane:<your-dataplane-name>

Placeholder	Description
`<jdbc-gateway-host>`	The JDBC gateway hostname for your xDP account — find this under Settings → Connection Info in the xDP UI.
`<catalog>`	The Trino catalog you want to query (e.g. a registered xStore or external datastore).
`<your-tenant-name>`	Your organization's tenant name in xDP.
`<your-dataplane-name>`	The name of the dataplane where this Trino instance runs.

Example connection

JDBC URL: jdbc:trino://<jdbc-gateway-host>:443/<catalog>?SSL=true&extraCredentials=tenant:<your-tenant-name>;dataplane:<your-dataplane-name> Username: <YOUR_ACCESS_KEY> Password: <YOUR_SECRET_KEY>

Enter these three values into your JDBC client's connection form exactly as your database credentials — the client doesn't need to know they originate from an xDP API key pair.

Supported connection parameters

Parameter	Location	Required	Description
`SSL`	Query string	Yes	Must be `true`. xDP's JDBC gateway only accepts encrypted connections.
`extraCredentials.tenant`	Query string	Yes	Routes the connection to your tenant.
`extraCredentials.dataplane`	Query string	Yes	Routes the connection to the specific dataplane running Trino.
Username	Connection auth	Yes	Your Access Key.
Password	Connection auth	Yes	Your Secret Key.

Tip: Treat your Access Key/Secret Key pair like a database password — never commit it to source control or share it outside your organization. Use a dedicated key pair per tool so you can revoke one integration without affecting others, and rotate immediately if a key is ever exposed.

Note: Most JDBC connection failures trace back to a mismatched tenant or dataplane value rather than the credentials themselves — confirm both before troubleshooting further.

Last updated on

Was this page helpful?