# Shared cookie SSO: Notifying frontend

**URL:** <https://meta.discourse.org/t/shared-cookie-sso-notifying-frontend/120012>\
**Category:** Development\
**Created:** [11.Июнь.2019 11:12:00 UTC](https://meta.discourse.org/t/shared-cookie-sso-notifying-frontend/120012 "2019-06-11T11:12:00Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [13.Июнь.2019 09:58:06 UTC](https://meta.discourse.org/t/shared-cookie-sso-notifying-frontend/120012/6 "2019-06-13T09:58:06Z")

</div>

The best solution here is to properly implement SSO.

If you do want to keep trying with the shared cookie, you can refresh the browser of a specific user using something like this integrated into your plugin:

```plaintext
MessageBus.publish "/file-change", ["refresh"], user_ids: [user.id]

```

I think this will require quite a lot of development to create a smooth user experience, and it’s beyond the scope of what we can provide support for. If I were you, I would spend the time creating a compatible SSO endpoint instead.

---

_[View the full topic](https://meta.discourse.org/t/shared-cookie-sso-notifying-frontend/120012)._
