# Native authentication showing up even if it is disabled

**URL:** <https://discuss.elastic.co/t/native-authentication-showing-up-even-if-it-is-disabled/91446>\
**Category:** Elasticsearch\
**Created:** [June 30, 2017, 2:16pm UTC](https://discuss.elastic.co/t/native-authentication-showing-up-even-if-it-is-disabled/91446 "2017-06-30T14:16:04Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [July 4, 2017, 7:58am UTC](https://discuss.elastic.co/t/native-authentication-showing-up-even-if-it-is-disabled/91446/2 "2017-07-04T07:58:11Z")

</div>

Hi @g-vamp,

It sounds very similar to what had been discussed here: [Disable login in Kibana 5.3](https://discuss.elastic.co/t/disable-login-in-kibana-5-3/82998).

In short, there are only 2 main possibilities to bypass Kibana login screen at the moment:

- Disable security entirely, likely it's not an option for you;
- Attribute your every request with proper `Authorization: Basic ***` HTTP header (if your realm supports `Basic` authentication of course). See the post above that explains how to do that with the help of reverse proxy.

Let me know if you still have questions.

Thanks,  
Oleg

---

_[View the full topic](https://discuss.elastic.co/t/native-authentication-showing-up-even-if-it-is-disabled/91446)._