Internal authentication
The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Stack
Generally available
Internal authentication methods are fully managed by Elasticsearch, and don't require any communication with external parties.
Elasticsearch offers two internal authentication realms, both of which are enabled by default. There can only be a maximum of one configured realm per internal realm type.
In this section, you'll learn how to configure internal realms, and manage users that authenticate using internal realms.
Elasticsearch provides two internal realm types:
- native
- Users are stored in a dedicated Elasticsearch index. This realm supports an authentication token in the form of username and password, and is available by default when no realms are explicitly configured. Users are managed through Kibana, or using user management APIs. See Native user authentication.
- file
- Users are defined in files stored on each node in the Elasticsearch cluster. This realm supports an authentication token in the form of username and password and is always available. See File-based user authentication. Available for Elastic Cloud on Kubernetes and self-managed deployments only.