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.
This commit is contained in:
parent
4102f419f8
commit
e928e4253d
|
@ -43,7 +43,7 @@
|
||||||
# the username and password that the Kibana server uses to perform maintenance on the Kibana
|
# 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
|
# index at startup. Your Kibana users still need to authenticate with Elasticsearch, which
|
||||||
# is proxied through the Kibana server.
|
# is proxied through the Kibana server.
|
||||||
#elasticsearch.username: "user"
|
#elasticsearch.username: "kibana"
|
||||||
#elasticsearch.password: "pass"
|
#elasticsearch.password: "pass"
|
||||||
|
|
||||||
# Enables SSL and paths to the PEM-format SSL certificate and SSL key files, respectively.
|
# Enables SSL and paths to the PEM-format SSL certificate and SSL key files, respectively.
|
||||||
|
|
Loading…
Reference in a new issue