Elasticsearch:Use X-Pack to configure LDAP authentication

Prerequisites

Precautions

Procedure

1. Step 1: (Optional) Obtain the domain name of an endpoint

2. Step 2: Configure LDAP authentication

3. Step 3: Map the user to a role

4. Step 4: Verify the result

Step 1: (Optional) Obtain the domain name of an endpoint

Elasticsearch clusters created in October 2020 or later are deployed in the new network architecture. These Elasticsearch clusters reside in the VPC of the Elasticsearch service account. If your Elasticsearch cluster is deployed in the new network architecture, you need to use the PrivateLink service to establish a private connection between the VPC and your VPC. Then, obtain the domain name of the related endpoint for future use. To obtain the domain name of an endpoint, perform the following steps:

1. Create a Classic Load Balancer (CLB) instance that supports the PrivateLink service and resides in the same VPC as the created Elasticsearch cluster.

   For more information, see Step 1: Create and configure a CLB instance.

2. Configure the CLB instance.

   During the configuration, you must specify the LDAP server as the backend server and port 389 as the listening port.

   For more information, see Configure a private connection for an Elasticsearch cluster.

3. Create an endpoint service.

   For more information, see Step 2: Create an endpoint service.

4. Configure a private connection to the Elasticsearch cluster.

   For more information, see Step 3: Create a private connection for the Elasticsearch cluster.

5. Obtain the domain name of the endpoint that is used to access the endpoint service.

   For more information, see Configure a private connection for an Elasticsearch cluster.

   Note Record the obtained domain name, which will be used in subsequent configurations.

Step 2: Configure LDAP authentication

The user search mode is commonly used. In user search mode, a user who has permissions to query the LDAP directory is used to search for the DN of a user who you want to authenticate. The search is performed based on the username and LDAP attribute that are provided by X-Pack. After the DN of the user is found, X-Pack attempts to bind the user to the LDAP directory by using the DN and the related password to authenticate the user. For more information, see Configure an LDAP realm.

For more information about the parameters, see Security settings in Elasticsearch.

Step 3: Map the user to a role

1. Log on to the Kibana console of your Elasticsearch cluster and go to the homepage of the Kibana console as prompted.

   For more information about how to log on to the Kibana console, see Log on to the Kibana console.

   Note

   In this example, an Elasticsearch V6.7.0 cluster is used. Operations on clusters of other versions may differ. The actual operations in the console prevail.

2. In the left-side navigation pane of the page that appears, click Dev Tools.

3. On the Console tab of the page that appears, run the following command to map the zhang* user to the administrator role:

   V8.X

   POST _security/role_mapping/ldap_super_user1?pretty
   {
     "roles": [ "superuser" ],
     "enabled": true,
     "rules": {
       "any": [
         {
           "field": {
             "username": "zhang*"
           }
         }
       ]
     }
   }

   Other versions

   POST _xpack/security/role_mapping/ldap_super_user1?pretty
   {
     "roles": [ "superuser" ],
     "enabled": true,
     "rules": {
       "any": [
         {
           "field": {
             "username": "zhang*"
           }
         }
       ]
     }
   }

   For more information, see Elastic versions.

Step 4: Verify the result

1. Log on to the Kibana console of the Elasticsearch cluster by using the zhang* user.

   

2. In the left-side navigation pane of the page that appears, click Dev Tools.

3. On the Console tab of the page that appears, run the following command to check whether the zhang* user has permissions to modify the configuration of the cluster:

   PUT _cluster/settings
   {
     "persistent": {
       "action.auto_create_index": true
     }
   }

   If the result shown in the following figure is returned, the user has permissions to modify the configuration of the cluster.