Elastic Search Basic Authentication

[Rifat_Erdem_Sahin (Erdem Sahin)]

After reading below i have decided to implement custom headers. I do not have x-pack security installed. Need a sample implementation as adding this did not sort out my issues

added this to kibana.yml
elasticsearch.customHeaders: { Authorization: Basic base64encoded un:pw }

##Option 2 - Kibana customHeaders
This solution is very similar to Option 1. Using the elasticsearch.customHeaders setting in the kibana.yml you can pass the same Basic Auth headers to Elasticsearch on every request. However, you'll have to disable X-Pack Security in Kibana for this option to work.
This solution doesn't require a reverse proxy; however, you will be forced to use Kibana as the same user, and disable X-Pack Security.

Reference

Kibana default basic auth

@ccrecana this behavior has been changed in 5.2.0, as this wasn't an intentional behavior. There are a few options to do what you're looking for, but first it might help to explain a bit of the background/details of Kibana/Elasticsearch auth. The way that authentication/authorization works with Elasticsearch via Kibana is two-fold. There is an internal user that Kibana uses to setup the initial .kibana index, the reporting queue, and various administrative features which is controlled by settin…