- 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.
Submitting Requests on Behalf of Other Users
editSubmitting Requests on Behalf of Other Users
editX-Pack security supports a permission that enables an authenticated user to submit requests on behalf of other users. If your application already authenticates users, you can use the run as mechanism to restrict data access according to X-Pack security permissions without having to re-authenticate each user through.
To "run as" (impersonate) another user, you must be able to retrieve the user from
the realm you use to authenticate. Both the internal native
and file
realms
support this out of the box. The LDAP realm must be configured to run in
user search mode. The Active Directory realm must be
configured with a bind_dn
and bind_password
to support run as.
The PKI realm does not support run as.
To submit requests on behalf of other users, you need to have the run_as
permission. For example, the following role grants permission to submit request
on behalf of jacknich
or redeniro
:
{ "run_as" : [ "jacknich", "rdeniro" ] }
To submit a request as another user, you specify the user in the
es-security-runas-user
request header. For example:
curl -H "es-security-runas-user: jacknich" -u es_admin -XGET 'http://localhost:9200/'
ElasticON events are back!
Learn about the Elastic Search AI Platform from the experts at our live events.
Register now