# Auto-authenticating to iframe-embedded Kibana dashboard

**URL:** <https://discuss.elastic.co/t/auto-authenticating-to-iframe-embedded-kibana-dashboard/46091>\
**Category:** Kibana\
**Created:** [April 1, 2016, 7:05pm UTC](https://discuss.elastic.co/t/auto-authenticating-to-iframe-embedded-kibana-dashboard/46091 "2016-04-01T19:05:20Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [January 12, 2017, 9:44pm UTC](https://discuss.elastic.co/t/auto-authenticating-to-iframe-embedded-kibana-dashboard/46091/6 "2017-01-12T21:44:08Z")

</div>

> @tsullivan Can it also be done on the [Elastic.co](http://Elastic.co) cloud?

I really don't know. [You and a colleague have been posting in another thread](https://discuss.elastic.co/t/auto-authenticating-to-an-embedded-kibana-dashboard-on-elastic-co-cloud/71248/6) about trying to do this, and according to messages there, you are getting this error:

```auto
{"ok":false,"message":"Unknown cluster."}

```

When you use Kibana hosted in Cloud normally, you are talking to a proxy, and that proxy has headers that it sets, including one for the cluster\_id. I don't know enough about this to know if your proxy might be preventing the Cloud proxy's header from persisting.

---

_[View the full topic](https://discuss.elastic.co/t/auto-authenticating-to-iframe-embedded-kibana-dashboard/46091)._