# Monitoring without Security 5.0A2

**URL:** <https://discuss.elastic.co/t/monitoring-without-security-5-0a2/49731>\
**Category:** Elasticsearch\
**Created:** [May 11, 2016, 7:28am UTC](https://discuss.elastic.co/t/monitoring-without-security-5-0a2/49731 "2016-05-11T07:28:26Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![gquintana](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gquintana/32/48441_2.png) [@gquintana](https://discuss.elastic.co/u/gquintana)\
**Post date:** [May 11, 2016, 7:28am UTC](https://discuss.elastic.co/t/monitoring-without-security-5-0a2/49731/1 "2016-05-11T07:28:26Z")

</div>

In the past for developping and testing I could install Marvel without Shield.

Now that they are bundled together, **I am forced to setup SSL certificates, user accounts** on my development laptop:  
Error: xpack.security.encryptionKey is required in kibana.yml.  
Error: HTTPS is required. Please set server.ssl.key and server.ssl.cert in kibana.yml.

IMHO, this is not user friendly.

Is there a workaround?

---

<div class="post-metadata">

**Author:** ![gquintana](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gquintana/32/48441_2.png) [@gquintana](https://discuss.elastic.co/u/gquintana)\
**Post date:** [May 11, 2016, 7:31am UTC](https://discuss.elastic.co/t/monitoring-without-security-5-0a2/49731/2 "2016-05-11T07:31:29Z")

</div>

Found the answer here: [https://www.elastic.co/guide/en/x-pack/current/installing-xpack.html](https://www.elastic.co/guide/en/x-pack/current/installing-xpack.html)

Installing the Kibana XPack plugin could add these default configs to kibana.yml

---

<div class="post-metadata">

**Author:** ![gquintana](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gquintana/32/48441_2.png) [@gquintana](https://discuss.elastic.co/u/gquintana)\
**Post date:** [May 11, 2016, 7:33am UTC](https://discuss.elastic.co/t/monitoring-without-security-5-0a2/49731/3 "2016-05-11T07:33:29Z")

</div>

After that I am stuck on the login page. These Kibana settings are not enough 😢

---

<div class="post-metadata">

**Author:** ![gquintana](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gquintana/32/48441_2.png) [@gquintana](https://discuss.elastic.co/u/gquintana)\
**Post date:** [May 11, 2016, 7:37am UTC](https://discuss.elastic.co/t/monitoring-without-security-5-0a2/49731/4 "2016-05-11T07:37:43Z")

</div>

The hidden solution is to had xpack.security.enabled: false in both Kibana et Elasticsearch config

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 1:41pm UTC](https://discuss.elastic.co/t/monitoring-without-security-5-0a2/49731/5 "2017-07-06T13:41:06Z")

</div>