LDAP authentication#
Trino can be configured to enable frontend LDAP authentication over HTTPS for clients, such as the Trino CLI, or the JDBC driver. At present, only simple LDAP authentication mechanism involving username and password is supported. The Trino client sends a username and password to the coordinator, and the coordinator validates these credentials using an external LDAP service.
To enable LDAP authentication for Trino, LDAP-related configuration changes are made on the Trino coordinator.
Using TLS and a configured shared secret is required for LDAP authentication.
Trino server configuration#
Trino coordinator node configuration#
Access to the Trino coordinator should be through HTTPS, configured as described on TLS and HTTPS.
You also need to make changes to the Trino configuration files.
LDAP authentication is configured on the coordinator in two parts.
The first part is to enable HTTPS support and password authentication
in the coordinator’s config.properties file. The second part is
to configure LDAP as the password authenticator plugin.
Server config properties#
The following is an example of the required properties that need to be added
to the coordinator’s config.properties file:
http-server.authentication.type=PASSWORD
http-server.https.enabled=true
http-server.https.port=8443
http-server.https.keystore.path=/etc/trino/keystore.jks
http-server.https.keystore.key=keystore_password
Property |
Description |
|---|---|
|
Enable the password authentication type
for the Trino coordinator. Must be set to |
|
Enables HTTPS access for the Trino coordinator.
Should be set to |
|
HTTPS server port. |
|
The location of the PEM or Java keystore file is used to enable TLS. |
|
The password for the PEM or Java keystore. This must match the password you specified when creating the PEM or keystore. |
|
Enable treating forwarded HTTPS requests over HTTP
as secure. Requires the |
|
Regex to match against user. If matched, user will be
replaced with first regex group. If not matched,
authentication is denied. Default is |
|
File containing rules for mapping user. See User mapping for more information. |
Password authenticator configuration#
Password authentication needs to be configured to use LDAP. Create an
etc/password-authenticator.properties file on the coordinator. Example:
password-authenticator.name=ldap
ldap.url=ldaps://ldap-server:636
ldap.ssl.truststore.path=/path/to/ldap_server.crt
ldap.user-bind-pattern=<Refer below for usage>
Property |
Description |
|---|---|
|
The URL to the LDAP server. The URL scheme must be
|
|
Allow using an LDAP connection that is not secured with TLS. |
|
Path to the PEM or JKS key store. |
|
Password for the key store. |
|
Path to the PEM or JKS trust store. |
|
Password for the trust store. |
|
This property can be used to specify the LDAP user
bind string for password authentication. This property
must contain the pattern The property can contain multiple patterns separated
by a colon. Each pattern will be checked in order
until a login succeeds or all logins fail. Example:
|
|
Ignore referrals to other LDAP servers while
performing search queries. Defaults to |
|
LDAP cache duration. Defaults to |
|
Timeout for establishing an LDAP connection. |
|
Timeout for reading data from an LDAP connection. |
Based on the LDAP server implementation type, the property
ldap.user-bind-pattern can be used as described below.
Active Directory#
ldap.user-bind-pattern=${USER}@<domain_name_of_the_server>
Example:
ldap.user-bind-pattern=${USER}@corp.example.com
OpenLDAP#
ldap.user-bind-pattern=uid=${USER},<distinguished_name_of_the_user>
Example:
ldap.user-bind-pattern=uid=${USER},OU=America,DC=corp,DC=example,DC=com
Trino CLI#
Environment configuration#
TLS configuration#
When using LDAP authentication, access to the Trino coordinator must be through TLS/HTTPS.
Trino CLI execution#
In addition to the options that are required when connecting to a Trino
coordinator that does not require LDAP authentication, invoking the CLI
with LDAP support enabled requires a number of additional command line
options. You can either use --keystore-* or --truststore-* properties
to secure TLS connection. The simplest way to invoke the CLI is with a
wrapper script.
#!/bin/bash
./trino \
--server https://trino-coordinator.example.com:8443 \
--keystore-path /tmp/trino.jks \
--keystore-password password \
--truststore-path /tmp/trino_truststore.jks \
--truststore-password password \
--catalog <catalog> \
--schema <schema> \
--user <LDAP user> \
--password
Find details on the options used in TLS/HTTPS and Username and password authentication.
Troubleshooting#
Java keystore file verification#
Verify the password for a keystore file and view its contents using Inspect and validate keystore.
Debug Trino to LDAP server issues#
If you need to debug issues with Trino communicating with the LDAP server, you can change the log level for the LDAP authenticator:
io.trino.plugin.password=DEBUG
TLS debugging for Trino CLI#
If you encounter any TLS related errors when running the Trino CLI, you can run
the CLI using the -Djavax.net.debug=ssl parameter for debugging. Use the
Trino CLI executable JAR to enable this. For example:
java -Djavax.net.debug=ssl \
-jar \
trino-cli-<version>-executable.jar \
--server https://coordinator:8443 \
<other_cli_arguments>
Common TLS/SSL errors#
java.security.cert.CertificateException: No subject alternative names present#
This error is seen when the Trino coordinator’s certificate is invalid, and does not have the IP you provide
in the --server argument of the CLI. You have to regenerate the coordinator’s TLS certificate
with the appropriate SAN added.
Adding a SAN to this certificate is required in cases where https:// uses IP address in the URL, rather
than the domain contained in the coordinator’s certificate, and the certificate does not contain the
SAN parameter with the matching IP address as an alternative attribute.
Authentication or TLS errors with JDK upgrade#
Starting with the JDK 8u181 release, to improve the robustness of LDAPS (secure LDAP over TLS) connections, endpoint identification algorithms were enabled by default. See release notes from Oracle. The same LDAP server certificate on the Trino coordinator, running on JDK version >= 8u181, that was previously able to successfully connect to an LDAPS server, may now fail with the following error:
javax.naming.CommunicationException: simple bind failed: ldapserver:636
[Root exception is javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No subject alternative DNS name matching ldapserver found.]
If you want to temporarily disable endpoint identification, you can add the
property -Dcom.sun.jndi.ldap.object.disableEndpointIdentification=true
to Trino’s jvm.config file. However, in a production environment, we
suggest fixing the issue by regenerating the LDAP server certificate so that
the certificate SAN or certificate subject
name matches the LDAP server.