Certificate authentication#

You can configure Trino to support client-provided certificates validated by the Trino server on initial connection.


This authentication method is only provided to support sites that have an absolute requirement for client authentication and already have client certificates for each client. Sites in this category have an existing PKI infrastructure, possibly including an onsite Certificate Authority (CA).

This feature is not appropriate for sites that need to generate a set of client certificates in order to use this authentication type. Consider instead using another authentication type.

Using TLS and a configured shared secret is required for certificate authentication.

Using certificate authentication#

All clients connecting with TLS/HTTPS go through the following initial steps:

  1. The client attempts to contact the coordinator.

  2. The coordinator returns its certificate to the client.

  3. The client validates the server’s certificate using the client’s trust store.

A cluster with certificate authentication enabled goes through the following additional steps:

  1. The coordinator asks the client for its certificate.

  2. The client responds with its certificate.

  3. The coordinator verifies the client’s certificate, using the coordinator’s trust store.

Several rules emerge from these steps:

  • Trust stores used by clients must include the certificate of the signer of the coordinator’s certificate.

  • Trust stores used by coordinators must include the certificate of the signer of client certificates.

  • The trust stores used by the coordinator and clients do not need to be the same.

  • The certificate that verifies the coordinator does not need to be the same as the certificate verifying clients.

Trino validates certificates based on the distinguished name (DN) from the X.509 Subject field. You can use user mapping to map the subject DN to a Trino user name.

There are three levels of client certificate support possible. From the point of view of the server:

  • The server does not require a certificate from clients.

  • The server asks for a certificate from clients, but allows connection without one.

  • The server must have a certificate from clients to allow connection.

Trino’s client certificate support is the middle type. It asks for a certificate but allows connection if another authentication method passes.

Certificate authentication configuration#

Enable certificate authentication by setting the Certificate authentication type in etc/config.properties:


You can specify certificate authentication along with another authenticaton method, such as PASSWORD. In this case, authentication is performed in the order of entries, and the first successful authentication results in access. For example, the following setting shows the use of two authentication types:


The following configuration properties are also available:

Configuration properties#

Property name



A regular expression pattern to map all user names for this authentication type to the format expected by Trino.


The path to a JSON file that contains a set of user mapping rules for this authentication type.

Use certificate authentication with clients#

When using the Trino CLI, specify the --keystore-path and --keystore-password options as described in Certificate authentication.

When using the Trino JDBC driver to connect to a cluster with certificate authentication enabled, use the SSLKeyStoreType and SSLKeyStorePassword parameters to specify the path to the client’s certificate and its password, if any.