Skip to content

Commit c717dcc

Browse files
committed
Replace tabs with spaces
1 parent 63764e0 commit c717dcc

File tree

1 file changed

+23
-23
lines changed
  • deploy-manage/users-roles/cluster-or-deployment-auth

1 file changed

+23
-23
lines changed

deploy-manage/users-roles/cluster-or-deployment-auth/pki.md

Lines changed: 23 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -47,9 +47,9 @@ To use PKI in {{es}}, you configure a PKI realm, enable client authentication on
4747
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 use one of the following methods to extract the username:
4848

4949
* {applies_to}`stack: ga 9.1` Extract the username from a specific RDN attribute in the Subject DN.
50-
* Using the [[username_pattern](elasticsearch://reference/elasticsearch/configuration-reference/security-settings.md#ref-pki-settings) setting, specify a regex to extract the desired username. The regex is applied on the Subject DN.
50+
* Using the [[username_pattern](elasticsearch://reference/elasticsearch/configuration-reference/security-settings.md#ref-pki-settings) setting, specify a regex to extract the desired username. The regex is applied on the Subject DN.
5151

52-
:::::{tab-set}
52+
:::::{tab-set}
5353

5454
::::{tab-item} Specific RDN attribute
5555
The username can be extracted from a specific RDN attribute in the Subject DN by using [username_rdn_name](elasticsearch://reference/elasticsearch/configuration-reference/security-settings.md#ref-pki-settings) or [username_rdn_oid](elasticsearch://reference/elasticsearch/configuration-reference/security-settings.md#ref-pki-settings). When an RDN attribute configuration is provided, it supersedes `username_pattern`.
@@ -68,27 +68,27 @@ To use PKI in {{es}}, you configure a PKI realm, enable client authentication on
6868
```
6969
::::
7070

71-
::::{tab-item} Regex
72-
Specify a regex to extract the desired username. The regex is applied on the Subject DN.
73-
74-
For example, the regex in the following configuration extracts the email address from the Subject DN:
75-
76-
```yaml
77-
xpack:
78-
security:
79-
authc:
80-
realms:
81-
pki:
82-
pki1:
83-
order: 1
84-
username_pattern: "EMAILADDRESS=(.*?)(?:,|$)"
85-
```
86-
:::{note}
87-
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.
88-
:::
89-
::::
90-
91-
:::::
71+
::::{tab-item} Regex
72+
Specify a regex to extract the desired username. The regex is applied on the Subject DN.
73+
74+
For example, the regex in the following configuration extracts the email address from the Subject DN:
75+
76+
```yaml
77+
xpack:
78+
security:
79+
authc:
80+
realms:
81+
pki:
82+
pki1:
83+
order: 1
84+
username_pattern: "EMAILADDRESS=(.*?)(?:,|$)"
85+
```
86+
:::{note}
87+
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.
88+
:::
89+
::::
90+
91+
:::::
9292

9393
3. Optional: If you want the same users to also be authenticated using certificates when they connect to {{kib}}, you must configure the {{es}} PKI realm to allow delegation. See [PKI authentication for clients connecting to {{kib}}](#pki-realm-for-proxied-clients).
9494
4. Restart {{es}} 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.

0 commit comments

Comments
 (0)