- X-Pack Reference for 6.0-6.2 and 5.x:
- Introduction
- Installing X-Pack
- Migrating to X-Pack
- Breaking Changes
- Breaking Changes in 5.5.2
- Breaking Changes in 5.5.0
- Breaking Changes in 5.3
- Breaking Changes in 5.2
- Breaking Changes in 5.0
- Breaking Changes in Shield 2.4.2
- Breaking Changes in Reporting 2.4.1
- Breaking Changes in Shield 2.4.0
- Breaking Changes in Shield 2.1.0
- Breaking Changes in Shield 2.0.1
- Breaking Changes in 2.0.0
- Breaking Changes in Shield 1.3.0
- X-Pack Settings
- X-Pack APIs
- Graphing Connections in Your Data
- Profiling your Queries and Aggregations
- Reporting from Kibana
- Securing Elasticsearch and Kibana
- Monitoring the Elastic Stack
- Alerting on Cluster and Index Events
- Machine Learning in the Elastic Stack
- Troubleshooting
- Limitations
- License Management
- Release Notes
WARNING: Version 5.6 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.
Enabling Anonymous Access
editEnabling Anonymous Access
editIncoming requests are considered to be anonymous if no authentication token
can be extracted from the incoming request. By default, anonymous requests are rejected and an authentication error is returned (status code 401
).
To enable anonymous access, you assign one or more roles to anonymous
users in the elasticsearch.yml
configuration file. For example, the following
configuration assigns anonymous users role1
and role2
:
The username/principal of the anonymous user. Defaults to
|
|
The roles to associate with the anonymous user. If no roles are specified, anonymous access is disabled—anonymous requests will be rejected and return an authentication error. |
|
When |