# Login problem after embeddding our Kibana Dashboard to an external site

**URL:** <https://discuss.elastic.co/t/login-problem-after-embeddding-our-kibana-dashboard-to-an-external-site/256878>\
**Category:** Kibana\
**Created:** [November 27, 2020, 12:45pm UTC](https://discuss.elastic.co/t/login-problem-after-embeddding-our-kibana-dashboard-to-an-external-site/256878 "2020-11-27T12:45:45Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gokul6](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gokul6/32/84049_2.png) [@Gokul6](https://discuss.elastic.co/u/Gokul6)\
**Post date:** [November 27, 2020, 12:45pm UTC](https://discuss.elastic.co/t/login-problem-after-embeddding-our-kibana-dashboard-to-an-external-site/256878/1 "2020-11-27T12:45:46Z")

</div>

We have a login problem after embeddding our Kibana Dashboard to an external site.  
After copying the iFrame code of a dashboard and embeddding it, when we try to login into Kibana the login page just gets reloaded and it's not letting us inside kibana. This issue is happening only when using google chrome but when  
we use firefox Kibana is working fine for us.

While searching a solution for this issue i found the below documentation from elasticsearch. How to solve this issue ?? please help 🙂

 ![sameSiteCookies](https://us1.discourse-cdn.com/elastic/original/3X/c/b/cba1c88698f03d5562f4fd3bca020d8e5b09daf9.png)

---

<div class="post-metadata">

**Author:** ![jportner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jportner/32/75692_2.png) [@jportner](https://discuss.elastic.co/u/jportner)\
**Post date:** [December 2, 2020, 2:31pm UTC](https://discuss.elastic.co/t/login-problem-after-embeddding-our-kibana-dashboard-to-an-external-site/256878/2 "2020-12-02T14:31:34Z")

</div>

This is happening because [Google changed Chrome](https://www.chromium.org/updates/same-site/faq) recently. It started treating the absence of a `SameSite` attribute as if it was `SameSite=Lax`.

The [SameSite attribute](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) instructs a browser that it should only send cookies to the same site.

You'll need to set this in your `kibana.yml` file:

```auto
xpack.security.sameSiteCookies: true
xpack.security.secureCookies: true

```

To use Secure Cookies you'll need SSL enabled on Kibana (e.g., the URL starts with "https://").  
If you don't already have SSL enabled, you can find out how to configure it [here](https://www.elastic.co/guide/en/kibana/current/configuring-tls.html#configuring-tls-browser-kib).

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 30, 2020, 2:31pm UTC](https://discuss.elastic.co/t/login-problem-after-embeddding-our-kibana-dashboard-to-an-external-site/256878/3 "2020-12-30T14:31:43Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.