# Authentication with Kibana in HTML Iframe
**URL:** https://discuss.elastic.co/t/authentication-with-kibana-in-html-iframe/186476
**Category:** Kibana
**Created:** [June 19, 2019, 1:31pm UTC](https://discuss.elastic.co/t/authentication-with-kibana-in-html-iframe/186476 "2019-06-19T13:31:05Z")
**Posts on this page:** 1
**Showing post:** 2
### Author:  [@lukas](https://discuss.elastic.co/u/lukas)
#### Post date: [June 19, 2019, 6:49pm UTC](https://discuss.elastic.co/t/authentication-with-kibana-in-html-iframe/186476/2 "2019-06-19T18:49:00Z")
Hi!
This is something that is frequently posted on the forums here. A quick search might be helpful here:
[https://discuss.elastic.co/search?q=iframe+authentication](https://discuss.elastic.co/search?q=iframe+authentication)
Specifically these:
> [@Authenticating to iframe-embedded Kibana dashboard](https://discuss.elastic.co/t/authenticating-to-iframe-embedded-kibana-dashboard/71129/7):
>
> Sorry for the delay, @rupaln and sorry for giving incomplete advice. I was able to get the Kibana server to respond with a cookie header by POSTing to /api/security/v1/login with a JSON request body of { "password": "\", "username": "\" } and the appropriate kbn-version: 5.1.1 header.
> [@Auto-authenticating to iframe-embedded Kibana dashboard](https://discuss.elastic.co/t/auto-authenticating-to-iframe-embedded-kibana-dashboard/46091/16):
>
> @tsullivan @Alex_Piggott @Francisca_Lima and others interested. Looks like you should use proxy\_set\_header Host $proxy\_host; instead of proxy\_set\_header Host $host; $proxy\_host takes host value from proxy\_pass directive, while $host will contain your server\_name. And apparently, Kibana from Elastic Cloud requires an original host to determine target cluster ID. Works for me without proxifying any additional X-Found-Cluster headers.
---
_[View the full topic](https://discuss.elastic.co/t/authentication-with-kibana-in-html-iframe/186476)._