# Kibana IFrame - Limit Data Searchable

**URL:** <https://discuss.elastic.co/t/kibana-iframe-limit-data-searchable/199799>\
**Category:** Kibana\
**Created:** [September 17, 2019, 10:05am UTC](https://discuss.elastic.co/t/kibana-iframe-limit-data-searchable/199799 "2019-09-17T10:05:04Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Larry\_Gregory](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/larry_gregory/32/34969_2.png) [@Larry\_Gregory](https://discuss.elastic.co/u/Larry_Gregory)\
**Post date:** [September 17, 2019, 2:47pm UTC](https://discuss.elastic.co/t/kibana-iframe-limit-data-searchable/199799/3 "2019-09-17T14:47:12Z")

</div>

I agree, using [document level security](https://www.elastic.co/guide/en/elastic-stack-overview/current/document-level-security.html) is the way to go here, but imbedding into an iframe certainly complicates matters.

If you don't want your users to have to authenticate, you can place a reverse-proxy such as nginx in front of Kibana, and have nginx supply the `Authorization` header of a fixed user account with document level security applied. Here's an example of such a configuration: [Auto-authenticating to iframe-embedded Kibana dashboard](https://discuss.elastic.co/t/auto-authenticating-to-iframe-embedded-kibana-dashboard/46091/4)

Otherwise, the iframes will end up rendering a login screen the first time, asking users to authenticate first. Once authenticated, you can have the same DLS rules applied.

---

_[View the full topic](https://discuss.elastic.co/t/kibana-iframe-limit-data-searchable/199799)._