- X-Pack Reference for 6.0-6.2 and 5.x:
- Introduction
- Setting Up X-Pack
- Breaking Changes
- X-Pack APIs
- Graphing Connections in Your Data
- Profiling your Queries and Aggregations
- Reporting from Kibana
- Securing the Elastic Stack
- Getting Started with Security
- How Security Works
- Setting Up User Authentication
- Configuring SAML Single-Sign-On on the Elastic Stack
- Configuring Role-based Access Control
- Auditing Security Events
- Encrypting Communications
- Restricting Connections with IP Filtering
- Cross Cluster Search, Tribe, Clients and Integrations
- Reference
- Monitoring the Elastic Stack
- Alerting on Cluster and Index Events
- Machine Learning in the Elastic Stack
- Troubleshooting
- Getting Help
- X-Pack security
- Can’t log in after upgrading to 6.2.4
- Some settings are not returned via the nodes settings API
- Authorization exceptions
- Users command fails due to extra arguments
- Users are frequently locked out of Active Directory
- Certificate verification fails for curl on Mac
- SSLHandshakeException causes connections to fail
- Common SSL/TLS exceptions
- Internal Server Error in Kibana
- Setup-passwords command fails due to connection failure
- X-Pack Watcher
- X-Pack monitoring
- X-Pack machine learning
- Limitations
- License Management
- Release Notes
WARNING: Version 6.2 of the Elastic Stack has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Native User Authentication
editNative User Authentication
editThe easiest way to manage and authenticate users is with the internal native
realm. You can use the REST APIs or Kibana to add and remove users, assign user roles, and
manage user passwords.
Configuring a Native Realm
editThe native realm is added to the realm chain by default. You don’t need to explicitly configure a native realm to manage users through the REST APIs.
When you configure realms in elasticsearch.yml
, only the
realms you specify are used for authentication. To use the
native
realm as a fallback, you must include it in the realm chain.
You can, however, configure options for the native
realm in the
xpack.security.authc.realms
namespace in elasticsearch.yml
. Explicitly
configuring a native realm enables you to set the order in which it appears in
the realm chain, temporary disable the realm, and control its cache options.
To configure a native realm:
-
Add a realm configuration of type
native
toelasticsearch.yml
under thexpack.security.authc.realms
namespace. At a minimum, you must set the realmtype
tonative
. If you are configuring multiple realms, you should also explicitly set theorder
attribute. See Native Realm Settings for all of the options you can set for thenative
realm.For example, the following snippet shows a
native
realm configuration that sets theorder
to zero so the realm is checked first:xpack: security: authc: realms: native1: type: native order: 0
- Restart Elasticsearch.
Native Realm Settings
editManaging Native Users
editX-Pack security enables you to easily manage users in Kibana on the Management / Security / Users page.
Alternatively, you can manage users through the user
API. For more
information and examples, see User Management APIs.
To migrate file-based users to the native
realm, use the
migrate tool.