Why is the non-existent `xpack.security.enabled` mentioned in Kibana's configuration documentation?

[linghengqian]

• Why is the non-existent xpack.security.enabled mentioned in Kibana's configuration documentation?
• See Run Elasticsearch locally in Docker (without security) | Elasticsearch Guide [8.15] | Elastic .

Start the Kibana container with the following command:

docker run -p 127.0.0.1:5601:5601 -d --name kibana --network elastic-net \
  -e ELASTICSEARCH_URL=http://elasticsearch:9200 \
  -e ELASTICSEARCH_HOSTS=http://elasticsearch:9200 \
  -e ELASTICSEARCH_USERNAME=kibana_system \
  -e ELASTICSEARCH_PASSWORD=$KIBANA_PASSWORD \
  -e "xpack.security.enabled=false" \
  -e "xpack.license.self_generated.type=trial" \
  docker.elastic.co/kibana/kibana:8.15.0

• But the problem is, xpack.security.enabled is not declared in Configure Kibana | Kibana Guide [8.15] | Elastic .
• According to Kibana 8.0.0-beta1 | Kibana Guide [8.15] | Elastic and Remove deprecated xpack.security.enabled config option by watson · Pull Request #111681 · elastic/kibana · GitHub, the xpack.security.enabled property has been removed.
• So what does setting xpack.security.enabled to false do in the Kibana container?

[bhavyarm]

@jbudz /@tiagocosta could you please grab this question?

Thanks,
Bhavya

[jbudz (Jon Budzenski)]

I opened a pull request to update our documentation at [docs] Remove xpack.security.enabled Kibana reference by jbudz · Pull Request #113894 · elastic/elasticsearch · GitHub.

So what does setting xpack.security.enabled to false do in the Kibana container?

The container will fail to start - thanks for noting this. It doesn't need to be configured.