# Disable login in Kibana 5.3

**URL:** <https://discuss.elastic.co/t/disable-login-in-kibana-5-3/82998>\
**Category:** Kibana\
**Created:** [April 20, 2017, 7:33am UTC](https://discuss.elastic.co/t/disable-login-in-kibana-5-3/82998 "2017-04-20T07:33:48Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Stacey\_Gammon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stacey_gammon/32/14025_2.png) [@Stacey\_Gammon](https://discuss.elastic.co/u/Stacey_Gammon)\
**Post date:** [April 20, 2017, 5:55pm UTC](https://discuss.elastic.co/t/disable-login-in-kibana-5-3/82998/2 "2017-04-20T17:55:11Z")

</div>

You can turn off security entirely, which will disable the login screen, by setting  
`xpack.security.enabled: false` in elasticsearch.yml and kibana.yml, but that may not be what need.

Is your goal to have users be automatically logged in with a certain role (say, read only?)?

The latter can be done with a reverse proxy. There is some good info on this here:

> [@Auto-authenticating to iframe-embedded Kibana dashboard](https://discuss.elastic.co/t/auto-authenticating-to-iframe-embedded-kibana-dashboard/46091/4):
>
> You can pass the Authorization header as Joe suggests using an nginx proxy. Here is the relevant section of my nginx.conf: server { listen 4443 ssl; # the default was port 443 server\_name tim-virtual-machine.local; ssl\_certificate /home/tim/domain.crt; ssl\_certificate\_key /home/tim/domain.key; ssl\_session\_cache shared:SSL:1m; ssl\_session\_timeout 5m; ssl\_ciphers HIGH:!aNULL:!MD5; ssl\_prefer\_server\_ciphers on; location / { …

As for the anonymous authentication, I'm not sure how kibana is supposed to act when that is set up in elasticsearch, but I'll try to find out more information.

---

_[View the full topic](https://discuss.elastic.co/t/disable-login-in-kibana-5-3/82998)._
