From e928e4253d97df212227ae3c4ea2d0339bf2e570 Mon Sep 17 00:00:00 2001 From: Brandon Kobel Date: Mon, 3 Jun 2019 08:58:03 -0700 Subject: [PATCH] Changing the example `elasticsearch.username` to "kibana" (#37717) (#37883) According to @tvernum, this is a common source of misconfiguration. Since we already recommend that users use the `kibana` reserved user for this setting, this should hopefully help some users out. --- config/kibana.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config/kibana.yml b/config/kibana.yml index 4abaf715f306..c19607d533c9 100644 --- a/config/kibana.yml +++ b/config/kibana.yml @@ -43,7 +43,7 @@ # the username and password that the Kibana server uses to perform maintenance on the Kibana # index at startup. Your Kibana users still need to authenticate with Elasticsearch, which # is proxied through the Kibana server. -#elasticsearch.username: "user" +#elasticsearch.username: "kibana" #elasticsearch.password: "pass" # Enables SSL and paths to the PEM-format SSL certificate and SSL key files, respectively.