Elasticsearch:Configure AD user authentication

Prerequisites

• An Alibaba Cloud Elasticsearch cluster is created.

  For more information, see Create an Alibaba Cloud Elasticsearch cluster. In this example, an Elasticsearch V7.10 cluster is created.

• An AD realm is created and configured on an Elastic Compute Service (ECS) instance that runs the Windows operating system and resides in the same virtual private cloud (VPC) as the Elasticsearch cluster. In this example, the Windows Server 2012 operating system is used. In addition, data is prepared.

  In this example, the ccy1 user and the ccy.com root realm are used.

Limits

Procedure

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

2. Step 2: Configure AD user 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 an SLB instance.

2. Configure the CLB instance.

   During the configuration, you must specify the Lightweight Directory Access Protocol (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: Configure 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 AD user authentication

An Elasticsearch cluster uses its security features to communicate with the AD realm and authenticate users. The security features communicate with the AD realm based on LDAP. An AD realm is similar to an LDAP realm. Like an LDAP directory, an AD realm stores users and groups in a hierarchical manner. An AD realm authenticates a user by sending an LDAP bind request. After the user passes the authentication, the AD realm searches for the entry of the user in the AD realm. After the AD realm finds the entry, the AD realm retrieves the group membership of the user from the tokenGroups attribute of the entry. For more information, see Configuring an Active Directory realm.

xpack.security.authc.realms.active_directory.my_ad.order: 2
xpack.security.authc.realms.active_directory.my_ad.domain_name: ccy.com
xpack.security.authc.realms.active_directory.my_ad.url: ldap://ep-bp1i321219*********-cn-hangzhou-h.epsrv-bp15571d5ps*********.cn-hangzhou.privatelink.aliyuncs.com:389
xpack.security.authc.realms.active_directory.my_ad.bind_dn: cc**@ccy.com
xpack.security.authc.realms.active_directory.my_ad.secure_bind_password: your_password

Step 3: Map the user to a role

1. Log on to the Kibana console of the Elasticsearch cluster.

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

   Note

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

2. Go to the homepage of the Kibana console as prompted and click Dev tools in the upper-right corner.

3. On the Console tab, run the following command to map the ccy1 user in the AD realm to the administrator role:

   PUT /_security/role_mapping/basic_users
   {
     "roles": [ "superuser" ],
     "enabled": true,
     "rules": {
       "any": [
         {
           "field": {
             "groups": "cn=ali,dc=ccy,dc=com"
           }
         },
         {
           "field": {
             "dn": "cn=ccy1,cn=ali,dc=ccy,dc=com"
           }
         }
       ]
     }
   }

Step 4: Verify the result

1. Use the ccy1 user to log on to the Kibana console of the Elasticsearch cluster.

2. Go to the homepage of the Kibana console as prompted and click Dev tools in the upper-right corner.

3. On the Console tab, run the following command to check whether the ccy1 user has permissions to perform the related operation:

   GET _cat/indices

   If permissions are granted to the ccy1 user, the result shown in the following figure is returned.