-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Closed
Labels
:Security/AuthenticationLogging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc)Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc)>bug>docsGeneral docs changesGeneral docs changesTeam:DocsMeta label for docs teamMeta label for docs teamTeam:SecurityMeta label for security teamMeta label for security team
Description
The File-based user authentication page at the same time states:
When you configure realms in elasticsearch.yml, only the realms you specify are used for authentication. To use the file realm you must explicitly include it in the realm chain. While it is possible to define multiple instances of some other realms, you can define only one file realm per node.
And
The file realm is added to the realm chain by default. You don’t need to explicitly configure a file realm.
- (Optional) Add a realm configuration to elasticsearch.yml under the xpack.security.authc.realms.file namespace. At a minimum, you must set the realm’s order attribute.
Obviously these snippets are contradictory. I am unaware of which one is correct, but the documentation needs updating anyway.
It seems the new information (the second snippet) was added on version 7.4.
Metadata
Metadata
Assignees
Labels
:Security/AuthenticationLogging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc)Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc)>bug>docsGeneral docs changesGeneral docs changesTeam:DocsMeta label for docs teamMeta label for docs teamTeam:SecurityMeta label for security teamMeta label for security team