New

The executive guide to generative AI

Read more
About usPartnersSupport|Login

WARNING: Version 5.5 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.

« Java Client and Security ES-Hadoop and Security »
Elastic Docs ›X-Pack for the Elastic Stack [5.5] ›Securing Elasticsearch and Kibana ›Cross Cluster Search, Tribe, Clients and Integrations

HTTP/REST Clients and Security

edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

HTTP/REST Clients and Security

edit

X-Pack security works with standard HTTP basic authentication headers to authenticate users. Since Elasticsearch is stateless, this header must be sent with every request:

Authorization: Basic <TOKEN>

The <TOKEN> is computed as base64(USERNAME:PASSWORD)

Client examples

edit

This example uses curl without basic auth to create an index:

curl -XPUT 'localhost:9200/idx'
{
  "error":  "AuthenticationException[Missing authentication token]",
  "status": 401
}

Since no user is associated with the request above, an authentication error is returned. Now we’ll use curl with basic auth to create an index as the rdeniro user:

curl --user rdeniro:taxidriver -XPUT 'localhost:9200/idx'
{
  "acknowledged": true
}

Client Libraries over HTTP

edit

For more information about how to use X-Pack security with the language specific clients please refer to Ruby, Python, Perl, PHP, .NET, Javascript

« Java Client and Security ES-Hadoop and Security »

On this page

Was this helpful?
Feedback