# Why is security setup so ridiculously awkward?

**URL:** <https://discuss.elastic.co/t/why-is-security-setup-so-ridiculously-awkward/359587>\
**Category:** Elasticsearch\
**Created:** [May 16, 2024, 5:18am UTC](https://discuss.elastic.co/t/why-is-security-setup-so-ridiculously-awkward/359587 "2024-05-16T05:18:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jimmymacGA](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jimmymacga/32/47144_2.png) [@jimmymacGA](https://discuss.elastic.co/u/jimmymacGA)\
**Post date:** [May 16, 2024, 5:18am UTC](https://discuss.elastic.co/t/why-is-security-setup-so-ridiculously-awkward/359587/1 "2024-05-16T05:18:06Z")

</div>

With each release of Elasticsearch, the security setup process gets more and more complex and less and less stable. Anytime the ES server is restarted, Kibana loses its ability to authenticate without generating a new token.

This setup process is absolute garbage and I wish you all would streamline it because this is piss poor behavior from a once great product.

---

<div class="post-metadata">

**Author:** ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)\
**Post date:** [May 17, 2024, 5:52am UTC](https://discuss.elastic.co/t/why-is-security-setup-so-ridiculously-awkward/359587/2 "2024-05-17T05:52:47Z")

</div>

> [@jimmymacGA](#):
>
> Anytime the ES server is restarted, Kibana loses its ability to authenticate without generating a new token.

That is not how the service tokens work. Perhaps you could open a topic about it and we can try and work out why you are seeing that behaviour.