# Inter-Discourse

**URL:** https://meta.discourse.org/t/inter-discourse/55598
**Category:** Feature
**Created:** [2017年一月11日 16:31 UTC](https://meta.discourse.org/t/inter-discourse/55598 "2017-01-11T16:31:10Z")
**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: [2017年一月11日 19:54 UTC](https://meta.discourse.org/t/inter-discourse/55598/2 "2017-01-11T19:54:14Z")

</div>

This is what SSO and social logins are for and already works.

> [@Use Discourse as an identity provider (SSO, DiscourseConnect)](https://meta.discourse.org/t/using-discourse-as-a-sso-provider/32974):
>
> So you want to use Discourse as an identity provider for your own web app? Great! Let’s get started. Enable [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) provider setting Under Discourse admin site settings (/admin/site\_settings) enable setting enable discourse connect provider and add a secret string to discourse connect provider secrets (used to hash SSO payloads). Implement [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) in your web app: Generate a random [nonce](https://en.wikipedia.org/wiki/Cryptographic_nonce). Let’s call this value NONCE. Save it temporarily so that you can verify it with the …

---

_[View the full topic](https://meta.discourse.org/t/inter-discourse/55598)._