Presto 325 Documentation

3.3. LDAP Authentication

3.3. LDAP Authentication

Presto can be configured to enable frontend LDAP authentication over HTTPS for clients, such as the Presto CLI, or the JDBC and ODBC drivers. At present, only simple LDAP authentication mechanism involving username and password is supported. The Presto 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 Presto, configuration changes are made on the Presto coordinator. No changes are required to the worker configuration; only the communication from the clients to the coordinator is authenticated. However, if you want to secure the communication between Presto nodes with SSL/TLS configure Secure Internal Communication.

Presto Server Configuration

Environment Configuration

Secure LDAP

Presto requires Secure LDAP (LDAPS), so make sure you have TLS enabled on your LDAP server.

TLS Configuration on Presto Coordinator

You need to import the LDAP server’s TLS certificate to the default Java truststore of the Presto coordinator to secure TLS connection. You can use the following example keytool command to import the certificate ldap_server.crt, to the truststore on the coordinator.

$ keytool -import -keystore <JAVA_HOME>/jre/lib/security/cacerts -trustcacerts -alias ldap_server -file ldap_server.crt

In addition to this, access to the Presto coordinator should be through HTTPS. You can do that by creating a Java Keystore File for TLS on the coordinator.

Presto Coordinator Node Configuration

You must make the following changes to the environment prior to configuring the Presto coordinator to use LDAP authentication and HTTPS.

You also need to make changes to the Presto 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 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 file:



Property Description
http-server.authentication.type Enable password authentication for the Presto coordinator. Must be set to PASSWORD.
http-server.https.enabled Enables HTTPS access for the Presto coordinator. Should be set to true. Default value is false.
http-server.https.port HTTPS server port.
http-server.https.keystore.path The location of the Java Keystore file that will be used to secure TLS.
http-server.https.keystore.key The password for the keystore. This must match the password you specified when creating the keystore.
http-server.authentication.allow-forwarded-https Enable treating forwarded HTTPS requests over HTTP as secure. Requires the X-Forwarded-Proto header to be set to https on forwarded requests. Default value is false.

Password Authenticator Configuration

Password authentication needs to be configured to use LDAP. Create an etc/ file on the coordinator. Example:
ldap.user-bind-pattern=<Refer below for usage>
Property Description
ldap.url The url to the LDAP server. The url scheme must be ldaps:// since Presto allows only Secure LDAP.
ldap.user-bind-pattern This property can be used to specify the LDAP user bind string for password authentication. This property must contain the pattern ${USER}, which is replaced by the actual username during the password authentication. Example: ${USER}

Based on the LDAP server implementation type, the property ldap.user-bind-pattern can be used as described below.

Active Directory





Authorization based on LDAP Group Membership

You can further restrict the set of users allowed to connect to the Presto coordinator, based on their group membership, by setting the optional and ldap.user-base-dn properties, in addition to the basic LDAP authentication properties.

Property Description
ldap.user-base-dn The base LDAP distinguished name for the user who tries to connect to the server. Example: OU=America,DC=corp,DC=example,DC=com This property is used to specify the LDAP query for the LDAP group membership authorization. This query is executed against the LDAP server and if successful, the user is authorized. This property must contain a pattern ${USER}, which is replaced by the actual username in the group authorization search query. See samples below.

Based on the LDAP server implementation type, the property can be used as described below.

Active Directory<objectclass_of_user>)(sAMAccountName=${USER})(memberof=<dn_of_the_authorized_group>))



For OpenLDAP, for this query to work, make sure you enable the memberOf overlay.

You can use this property for scenarios where you want to authorize a user based on complex group authorization search queries. For example, if you want to authorize a user belonging to any one of multiple groups (in OpenLDAP), this property may be set as follows:|(memberOf=CN=normal_group,DC=corp,DC=com)(memberOf=CN=another_group,DC=com))(objectClass=inetOrgPerson)(uid=${USER}))

Presto CLI

Environment Configuration

TLS Configuration

Access to the Presto coordinator should be through HTTPS when using LDAP authentication. The Presto CLI can use either a Java Keystore file or Java Truststore for its TLS configuration.

If you are using a keystore file, it can be copied to the client machine and used for its TLS configuration. If you are using truststore, you can either use default Java truststores or create a custom truststore on the CLI. We do not recommend using self-signed certificates in production.

Presto CLI Execution

In addition to the options that are required when connecting to a Presto 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.


./presto \
--server \
--keystore-path /tmp/presto.jks \
--keystore-password password \
--truststore-path /tmp/presto_truststore.jks \
--truststore-password password \
--catalog <catalog> \
--schema <schema> \
--user <LDAP user> \
Option Description
--server The address and port of the Presto coordinator. The port must be set to the port the Presto coordinator is listening for HTTPS connections on. Presto CLI does not support using http scheme for the url when using LDAP authentication.
--keystore-path The location of the Java Keystore file that will be used to secure TLS.
--keystore-password The password for the keystore. This must match the password you specified when creating the keystore.
--truststore-path The location of the Java Truststore file that will be used to secure TLS.
--truststore-password The password for the truststore. This must match the password you specified when creating the truststore.
--user The LDAP username. For Active Directory this should be your sAMAccountName and for OpenLDAP this should be the uid of the user. This is the username which is used to replace the ${USER} placeholder pattern in the properties specified in
--password Prompts for a password for the user.


Java Keystore File Verification

Verify the password for a keystore file and view its contents using Java Keystore File Verification.

SSL Debugging for Presto CLI

If you encounter any SSL related errors when running Presto CLI, you can run CLI using parameter for debugging. You should use the Presto CLI executable jar to enable this. E.g.:

java \
-jar \
presto-cli-<version>-executable.jar \
--server https://coordinator:8443 \

Common SSL errors No subject alternative names present

This error is seen when the Presto 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 SSL 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 SSL errors with JDK Upgrade

Starting with the JDK 8u181 release, to improve the robustness of LDAPS (secure LDAP over TLS) connections, endpoint identification algorithms have been enabled by default. See release notes from Oracle. The same LDAP server certificate on the Presto coordinator, running on JDK version >= 8u181, that was previously able to successfully connect to an LDAPS server, may now fail with the below error:

javax.naming.CommunicationException: simple bind failed: ldapserver:636
[Root exception is 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 Presto’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.