Skip to content

fix minor issues in cluster auth docs #2478

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 8, 2025
Merged

fix minor issues in cluster auth docs #2478

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cc93705
fix minor issues in cluster auth docs
richard-dennehy Aug 8, 2025
fab63f1
Merge branch 'main' into auth-docs-fixes
richard-dennehy Aug 8, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion deploy-manage/users-roles/cluster-or-deployment-auth/external-authentication.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ External authentication in Elastic is any form of authentication that requires i

Elastic offers several external [realm](authentication-realms.md) types, each of which represents a common authentication provider. You can have as many external realms as you would like, each with its own unique name and configuration.

If the authentication provider that you want to use is not currently supported, then you can create a your own [custom realm plugin](custom.md) to integrate with additional systems.
If the authentication provider that you want to use is not currently supported, then you can create your own [custom realm plugin](custom.md) to integrate with additional systems.

In this section, you'll learn how to configure different types of external realms, and use them to grant access to Elastic resources.

Expand Down
2 changes: 1 addition & 1 deletion deploy-manage/users-roles/cluster-or-deployment-auth/jwt.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -284,7 +284,7 @@ You can relax validation of any of the time-based claims by setting `allowed_clo

## Role mapping [jwt-authorization]

You can map LDAP groups to roles in the following ways:
You can map JWT groups to roles in the following ways:

* Using the role mappings page in {{kib}}.
* Using the [role mapping API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-security-put-role-mapping).
Expand Down
2 changes: 1 addition & 1 deletion deploy-manage/users-roles/cluster-or-deployment-auth/ldap.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ The path to an entry is a *Distinguished Name* (DN) that uniquely identifies a u
The `ldap` realm supports two modes of operation, a user search mode and a mode with specific templates for user DNs.

::::{important}
When you configure realms in `elasticsearch.yml`/deploy-manage/stack-settings.md, 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.
When you configure realms in [`elasticsearch.yml`](/deploy-manage/stack-settings.md), 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.
::::

## Step 1: Add a new realm configuration [ldap-realm-configuration]
Expand Down
Loading