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

**URL:** <https://discuss.elastic.co/t/why-is-the-non-existent-xpack-security-enabled-mentioned-in-kibanas-configuration-documentation/366131>\
**Category:** Kibana\
**Tags:** docker\
**Created:** [September 6, 2024, 4:46am UTC](https://discuss.elastic.co/t/why-is-the-non-existent-xpack-security-enabled-mentioned-in-kibanas-configuration-documentation/366131 "2024-09-06T04:46:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![linghengqian](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/linghengqian/32/103651_2.png) [@linghengqian](https://discuss.elastic.co/u/linghengqian)\
**Post date:** [September 6, 2024, 4:46am UTC](https://discuss.elastic.co/t/why-is-the-non-existent-xpack-security-enabled-mentioned-in-kibanas-configuration-documentation/366131/1 "2024-09-06T04:46:29Z")

</div>

- 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](https://www.elastic.co/guide/en/elasticsearch/reference/current/run-elasticsearch-locally.html#local-dev-run-kib) .

> Start the Kibana container with the following command:

```bash
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](https://www.elastic.co/guide/en/kibana/current/settings.html) .
- According to [Kibana 8.0.0-beta1 | Kibana Guide [8.15] | Elastic](https://www.elastic.co/guide/en/kibana/current/release-notes-8.0.0-beta1.html#platform-breaking-changes-8.0.0-beta1) and [Remove deprecated xpack.security.enabled config option by watson · Pull Request #111681 · elastic/kibana · GitHub](https://github.com/elastic/kibana/pull/111681), the `xpack.security.enabled` property has been removed.
- So what does setting `xpack.security.enabled` to `false` do in the Kibana container?

---

<div class="post-metadata">

**Author:** ![bhavyarm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavyarm/32/22392_2.png) [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)\
**Post date:** [October 1, 2024, 6:02pm UTC](https://discuss.elastic.co/t/why-is-the-non-existent-xpack-security-enabled-mentioned-in-kibanas-configuration-documentation/366131/2 "2024-10-01T18:02:08Z")

</div>

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

Thanks,  
Bhavya

---

<div class="post-metadata">

**Author:** ![jbudz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jbudz/32/45922_2.png) [@jbudz](https://discuss.elastic.co/u/jbudz)\
**Post date:** [October 1, 2024, 7:49pm UTC](https://discuss.elastic.co/t/why-is-the-non-existent-xpack-security-enabled-mentioned-in-kibanas-configuration-documentation/366131/3 "2024-10-01T19:49:49Z")

</div>

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](https://github.com/elastic/elasticsearch/pull/113894).

> 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.