# Shared cookie SSO: Notifying frontend

**URL:** https://meta.discourse.org/t/shared-cookie-sso-notifying-frontend/120012
**Category:** Development
**Created:** [June 11, 2019, 11:12am UTC](https://meta.discourse.org/t/shared-cookie-sso-notifying-frontend/120012 "2019-06-11T11:12:00Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [June 12, 2019, 1:55pm UTC](https://meta.discourse.org/t/shared-cookie-sso-notifying-frontend/120012/2 "2019-06-12T13:55:32Z")

</div>

Why are you not using the built in SSO support?

> [@Setup DiscourseConnect - Official Single-Sign-On for Discourse (sso)](https://meta.discourse.org/t/official-single-sign-on-for-discourse-sso/13045):
>
> [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) is a core Discourse feature that allows you to configure “Single Sign-On (SSO)” to completely outsource all user registration and login from Discourse to another site. Offered to our [pro, business and enterprise hosting customers](https://discourse.org/pricing). information_source (Feb 2021) ‘[Discourse SSO](https://meta.discourse.org/t/13045?silent=true)’ is now ‘[DiscourseConnect](https://meta.discourse.org/t/13045?silent=true)’. If you are running an old version of Discourse, the settings below will be named sso\_... rather than discourse\_connect\_... The Problem Many sites wishing to integrate wit…

---

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