---
title: PKI
description: You can configure Elasticsearch to use Public Key Infrastructure (PKI) certificates to authenticate users. In this scenario, clients connecting directly...
url: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4232/deploy-manage/users-roles/cluster-or-deployment-auth/pki
products:
  - Elasticsearch
---

# PKI
<warning>
  This type of user authentication cannot be configured on Elastic Cloud Hosted deployments.
</warning>

You can configure Elasticsearch to use Public Key Infrastructure (PKI) certificates to authenticate users. In this scenario, clients connecting directly to Elasticsearch must present X.509 certificates. First, the certificates must be accepted for authentication on the SSL/TLS layer on Elasticsearch. Then they are optionally further validated by a PKI realm. See [PKI authentication for clients connecting directly to Elasticsearch](#pki-realm-for-direct-clients).
You can also use PKI certificates to authenticate to Kibana, however this requires some additional configuration. On Elasticsearch, this configuration enables Kibana to act as a proxy for SSL/TLS authentication and to submit the client certificates to Elasticsearch for further validation by a PKI realm. See [PKI authentication for clients connecting to Kibana](#pki-realm-for-proxied-clients).

## PKI authentication for clients connecting directly to Elasticsearch

To use PKI in Elasticsearch, you configure a PKI realm, enable client authentication on the desired network layers (transport or http), and map the Distinguished Names (DNs) from the `Subject` field in the user certificates to roles. You create the mappings in a role mapping file or use the role mappings API.
1. Add a realm configuration for a `pki` realm to [`elasticsearch.yml`](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4232/deploy-manage/stack-settings) under the `xpack.security.authc.realms.pki` namespace. You must explicitly set the `order` attribute. See [PKI realm settings](https://docs-v3-preview.elastic.dev/elastic/elasticsearch/tree/main/reference/elasticsearch/configuration-reference/security-settings#ref-pki-settings) for all of the options you can set for a `pki` realm.
   For example, the following snippet shows the most basic `pki` realm configuration:
   ```yaml
   xpack:
     security:
       authc:
         realms:
           pki:
             pki1:
               order: 1
   ```
   With this configuration, any certificate trusted by the Elasticsearch SSL/TLS layer is accepted for authentication. The username is the common name (CN) extracted from the DN in the Subject field of the end-entity certificate. This configuration is not sufficient to permit PKI authentication to Kibana; additional steps are required.
   <important>
   When you configure realms in `elasticsearch.yml`, only the realms you specify are used for authentication. If you also want to use the `native` or `file` realms, you must include them in the realm chain.
   </important>
2. Optional: The username is defined by the [username_pattern](https://docs-v3-preview.elastic.dev/elastic/elasticsearch/tree/main/reference/elasticsearch/configuration-reference/security-settings#ref-pki-settings). If you want to use something other than the CN of the Subject DN as the username, you can specify a regex to extract the desired username. The regex is applied on the Subject DN.
   For example, the regex in the following configuration extracts the email address from the Subject DN:
   ```yaml
   xpack:
     security:
       authc:
         realms:
           pki:
             pki1:
               order: 1
               username_pattern: "EMAILADDRESS=(.*?)(?:,|$)"
   ```
   <note>
   If the regex is too restrictive and does not match the Subject DN of the client’s certificate, then the realm does not authenticate the certificate.
   </note>
3. Optional: If you want the same users to also be authenticated using certificates when they connect to Kibana, you must configure the Elasticsearch PKI realm to allow delegation. See [PKI authentication for clients connecting to Kibana](#pki-realm-for-proxied-clients).
4. Restart Elasticsearch because realm configuration is not reloaded automatically. If you’re following through with the next steps, you might wish to hold the restart for last.
5. If you're using a self-managed cluster, then [enable SSL/TLS](/elastic/docs-content/pull/4232/deploy-manage/security/secure-cluster-communications#encrypt-internode-communication).
6. If you're using a self-managed cluster or Elastic Cloud on Kubernetes, then enable client authentication on the desired network layers (transport or http).
   <important>
   To use PKI when clients connect directly to Elasticsearch, you must enable SSL/TLS with client authentication by setting `xpack.security.transport.ssl.client_authentication` and `xpack.security.http.ssl.client_authentication` to `optional` or `required`. If the setting value is `optional`, clients without certificates can authenticate with other credentials.
   </important>
   When clients connect directly to Elasticsearch and are not proxy-authenticated, the PKI realm relies on the TLS settings of the node’s network interface. The realm can be configured to be more restrictive than the underlying network connection. That is, it is possible to configure the node such that some connections are accepted by the network interface but then fail to be authenticated by the PKI realm. However, the reverse is not possible. The PKI realm cannot authenticate a connection that has been refused by the network interface.
   In particular this means:
   - The transport or http interface must request client certificates by setting `client_authentication` to `optional` or `required`.
- The interface must *trust* the certificate that is presented by the client by configuring either the `truststore` or `certificate_authorities` paths, or by setting `verification_mode` to `none`.
- The *protocols* supported by the interface must be compatible with those used by the client.
   For an explanation of these settings, see [General TLS settings](https://docs-v3-preview.elastic.dev/elastic/elasticsearch/tree/main/reference/elasticsearch/configuration-reference/security-settings#ssl-tls-settings).
7. Optional: Configure the PKI realm to trust a subset of certificates.
   The relevant network interface (transport or http) must be configured to trust any certificate that is to be used within the PKI realm. However, it is possible to configure the PKI realm to trust only a *subset* of the certificates accepted by the network interface. This is useful when the SSL/TLS layer trusts clients with certificates that are signed by a different CA than the one that signs your users' certificates.
   1. To configure the PKI realm with its own trust store, specify the `truststore.path` option. The path must be located within the Elasticsearch configuration directory (`ES_PATH_CONF`). For example:
   ```yaml
   xpack:
     security:
       authc:
         realms:
           pki:
             pki1:
               order: 1
               truststore:
                 path: "pki1_truststore.jks"
   ```
   <tip>
   If you're using Elastic Cloud Enterprise or Elastic Cloud Hosted, then you must [upload this file as a custom bundle](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4232/deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles) before it can be referenced.If you're using Elastic Cloud on Kubernetes, then install the file as a [custom configuration file](/elastic/docs-content/pull/4232/deploy-manage/deploy/cloud-on-k8s/custom-configuration-files-plugins#use-a-volume-and-volume-mount-together-with-a-configmap-or-secret).If you're using a self-managed cluster, then the file must be present on each node.
   </tip>
   The `certificate_authorities` option can be used as an alternative to the `truststore.path` setting, when the certificate files are PEM formatted. The setting accepts a list. The two options are exclusive, they cannot be both used simultaneously.
   1. If the trust store is password protected, the password should be configured by adding the appropriate `secure_password` setting [to the Elasticsearch keystore](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4232/deploy-manage/security/secure-settings). For example, in a self-managed cluster, the following command adds the password for the example realm above:
   ```shell
   bin/elasticsearch-keystore add \
   xpack.security.authc.realms.pki.pki1.truststore.secure_password
   ```
8. Map roles for PKI users.
   You map roles for PKI users through the [role mapping APIs](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-security) or by using a file. Both configuration options are merged together. When a user authenticates against a PKI realm, the privileges for that user are the union of all privileges defined by the roles to which the user is mapped.
   You identify a user by the distinguished name in their certificate. For example, the following mapping configuration maps `John Doe` to the `user` role using the role mapping API:
   ```json

   {
     "roles" : [ "user" ],
     "rules" : { "field" : {
       "dn" : "cn=John Doe,ou=example,o=com" <1>
     } },
     "enabled": true
   }
   ```
   Alternatively, use a role-mapping file. For example:
   ```yaml
   user: 
     - "cn=John Doe,ou=example,o=com" 
   ```
   <tip>
   If you're using Elastic Cloud Enterprise or Elastic Cloud Hosted, then you must [upload this file as a custom bundle](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4232/deploy-manage/deploy/elastic-cloud/upload-custom-plugins-bundles) before it can be referenced.If you're using Elastic Cloud on Kubernetes, then install the file as a [custom configuration file](/elastic/docs-content/pull/4232/deploy-manage/deploy/cloud-on-k8s/custom-configuration-files-plugins#use-a-volume-and-volume-mount-together-with-a-configmap-or-secret).If you're using a self-managed cluster, then the file must be present on each node.
   </tip>
   The file’s path defaults to `ES_PATH_CONF/role_mapping.yml`. You can specify a different path (which must be within `ES_PATH_CONF`) by using the `files.role_mapping` realm setting (e.g. `xpack.security.authc.realms.pki.pki1.files.role_mapping`).
   The distinguished name for a PKI user follows X.500 naming conventions which place the most specific fields (like `cn` or `uid`) at the beginning of the name and the most general fields (like `o` or `dc`) at the end of the name. Some tools, such as *openssl*, may print out the subject name in a different format.
   One way that you can determine the correct DN for a certificate is to use the [authenticate API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-security-authenticate) (use the relevant PKI certificate as the means of authentication) and inspect the metadata field in the result. The user’s distinguished name will be populated under the `pki_dn` key. You can also use the authenticate API to validate your role mapping.
   For more information, see [Mapping users and groups to roles](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4232/deploy-manage/users-roles/cluster-or-deployment-auth/mapping-users-groups-to-roles).
   <note>
   The PKI realm supports [authorization realms](/elastic/docs-content/pull/4232/deploy-manage/users-roles/cluster-or-deployment-auth/realm-chains#authorization_realms) as an alternative to role mapping.
   </note>


## PKI authentication for clients connecting to Kibana

By default, the PKI realm relies on the node’s network interface to perform the SSL/TLS handshake and extract the client certificate. This behavior requires that clients connect directly to Elasticsearch so that their SSL connection is terminated by the Elasticsearch node. If SSL/TLS authentication is to be performed by Kibana, the PKI realm must be configured to permit delegation.
Specifically, when clients presenting X.509 certificates connect to Kibana, Kibana performs the SSL/TLS authentication. Kibana then forwards the client’s certificate chain (by calling an Elasticsearch API) to have them further validated by the PKI realms that have been configured for delegation.
To permit authentication delegation for a specific Elasticsearch PKI realm, start by [configuring the realm](#pki-realm-for-direct-clients). In this scenario, for self-managed clusters, it is mandatory that you [encrypt HTTP client communications](/elastic/docs-content/pull/4232/deploy-manage/security/secure-cluster-communications#encrypt-http-communication) when you enable TLS.
You must also explicitly configure a `truststore` (or, equivalently `certificate_authorities`) even though it is the same trust configuration that you have configured on the network layer. The `xpack.security.authc.token.enabled` and `delegation.enabled` settings must also be `true`. For example:
```yaml
xpack:
  security:
    authc:
      token.enabled: true
      realms:
        pki:
          pki1:
            order: 1
            delegation.enabled: true
            truststore:
              path: "pki1_truststore.jks"
```

After you restart Elasticsearch, this realm can validate delegated PKI authentication. You must then [configure Kibana to allow PKI certificate authentication](/elastic/docs-content/pull/4232/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-authentication#pki-authentication).
A PKI realm with `delegation.enabled` still works unchanged for clients connecting directly to Elasticsearch. Directly authenticated users and users that are PKI authenticated by delegation to Kibana both follow the same [role mapping rules](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4232/deploy-manage/users-roles/cluster-or-deployment-auth/mapping-users-groups-to-roles) or [authorization realms configurations](/elastic/docs-content/pull/4232/deploy-manage/users-roles/cluster-or-deployment-auth/realm-chains#authorization_realms).
If you use the [role mapping APIs](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-security), however, you can distinguish between users that are authenticated by delegation and users that are authenticated directly. The former have the extra fields `pki_delegated_by_user` and `pki_delegated_by_realm` in the user’s metadata. In the common setup, where authentication is delegated to Kibana, the values of these fields are `kibana` and `reserved`, respectively. For example, the following role mapping rule assigns the `role_for_pki1_direct` role to all users that have been authenticated directly by the `pki1` realm, by connecting to Elasticsearch instead of going through Kibana:
```json

{
  "roles" : [ "role_for_pki1_direct" ],
  "rules" : {
    "all": [
      {
        "field": {"realm.name": "pki1"}
      },
      {
        "field": {
          "metadata.pki_delegated_by_user": null <1>
        }
      }
    ]
  },
  "enabled": true
}
```


## Use PKI authentication for Kibana

If you want to use PKI authentication to authenticate using your browser and Kibana, you need to enable the relevant authentication provider in Kibana configuration. See [Kibana authentication](/elastic/docs-content/pull/4232/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-authentication#pki-authentication).