# Missing security options after enabling security in 7.3 ELK Stack

**URL:** https://discuss.elastic.co/t/missing-security-options-after-enabling-security-in-7-3-elk-stack/198655
**Category:** Kibana
**Created:** [September 9, 2019, 9:58am UTC](https://discuss.elastic.co/t/missing-security-options-after-enabling-security-in-7-3-elk-stack/198655 "2019-09-09T09:58:50Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![KervyN](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kervyn/32/10617_2.png) [@KervyN](https://discuss.elastic.co/u/KervyN)
#### Post date: [September 9, 2019, 9:58am UTC](https://discuss.elastic.co/t/missing-security-options-after-enabling-security-in-7-3-elk-stack/198655/1 "2019-09-09T09:58:50Z")

</div>

So, after reading that the security features came to ES for free I tried to set it up.

I went through the how to here: [https://www.elastic.co/guide/en/elastic-stack-overview/current/security-getting-started.html](https://www.elastic.co/guide/en/elastic-stack-overview/current/security-getting-started.html)

But it looks like there is no **Management / Security / Users** page in Kibana. I am authenticated with the elastic user.

Any ideas what I am doing wrong?

License is basic  
Version is 7.3.1

Cheers

---

<div class="post-metadata">

### Author: ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)
#### Post date: [September 10, 2019, 4:03pm UTC](https://discuss.elastic.co/t/missing-security-options-after-enabling-security-in-7-3-elk-stack/198655/2 "2019-09-10T16:03:19Z")

</div>

Hey @KervyN,

Can you share the screenshot of the management screen: [http://localhost:5601/app/kibana#/management](http://localhost:5601/app/kibana#/management) (assuming you're running at `http://localhost:5601`)?

Also what do you see if you try to go to `roles` page directly: [http://localhost:5601/app/kibana#/management/security/roles](http://localhost:5601/app/kibana#/management/security/roles)?

If you set `xpack.security.enabled: true` in `config.yml` of Elasticsearch and set up all the passwords it should work out of the box..... Let's see.

Best,  
Oleg

---

<div class="post-metadata">

### Author: ![KervyN](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kervyn/32/10617_2.png) [@KervyN](https://discuss.elastic.co/u/KervyN)
#### Post date: [September 10, 2019, 4:54pm UTC](https://discuss.elastic.co/t/missing-security-options-after-enabling-security-in-7-3-elk-stack/198655/3 "2019-09-10T16:54:20Z")

</div>

Hi,  
I connect via nginx proxy, but this is just "map port 5601 to port 443 with ssl".  
Here the screenshot:

 ![grafik](https://us1.discourse-cdn.com/elastic/original/3X/7/2/72d8a6cec444078a9528d619f083ed8102cea336.png)

When I go to `/app/kibana#/management/security/roles` I got redirected to `/app/kibana#/home?_g=()`

```
# grep xpack /etc/elasticsearch/elasticsearch.yml
xpack.security.enabled: true

```

I use the user `elastic` to open Kibana with the password which was generated by `/usr/share/elasticsearch/bin/elasticsearch-setup-passwords auto`

If this matters:  
The elk cluster was freshly set up 4-5 month ago and just updated via apt from time to time. I don't know if I fucked up some config while trying to get elk with filebeat running. I've just set up a pipeline which removes the client ip address when I reindex after 7 days.  
Logstash sends logs to requests-.

---

<div class="post-metadata">

### Author: ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)
#### Post date: [September 10, 2019, 5:26pm UTC](https://discuss.elastic.co/t/missing-security-options-after-enabling-security-in-7-3-elk-stack/198655/4 "2019-09-10T17:26:18Z")

</div>

> [@KervyN](#):
>
> I use the user `elastic` to open Kibana with the password

Did you log in with Kibana own login page or with browser native "basic auth" dialog? I've been suggested that you might have disabled security plugin in Kibana, can you check that you **don't** have `xpack.security.enabled: false` in `kibana.yml`?

Also if you used browser native username/password dialog you may need to close browser at some point as browsers tend to cache that info that can lead to all sort of issues.

---

<div class="post-metadata">

### Author: ![KervyN](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kervyn/32/10617_2.png) [@KervyN](https://discuss.elastic.co/u/KervyN)
#### Post date: [September 11, 2019, 7:12am UTC](https://discuss.elastic.co/t/missing-security-options-after-enabling-security-in-7-3-elk-stack/198655/5 "2019-09-11T07:12:25Z")

</div>

HA!

got ya

```
# grep xpack /etc/kibana/kibana.yml
xpack.security.encryptionKey: "mystrongkeywhichshouldbe32bytelong"
xpack.security.enabled: false

```

I removed the option from kibana.yml and restartet kibana **AND THERE IT IS**.  
Thank you a lot \<3

Even with the basic auth it worked, but now I got this beautiful login screen where 1password can fill the password. Oh thats so beautiful.

---

<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: [October 9, 2019, 7:12am UTC](https://discuss.elastic.co/t/missing-security-options-after-enabling-security-in-7-3-elk-stack/198655/6 "2019-10-09T07:12:49Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
