# Discourse a SSO provider for Wordpress

**URL:** <https://meta.discourse.org/t/discourse-a-sso-provider-for-wordpress/29934>\
**Category:** WordPress\
**Created:** [2015年六月12日 14:55 UTC](https://meta.discourse.org/t/discourse-a-sso-provider-for-wordpress/29934 "2015-06-12T14:55:41Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![erlend\_sh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/erlend_sh/32/119475_2.png) [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)\
**Post date:** [2016年十月5日 19:49 UTC](https://meta.discourse.org/t/discourse-a-sso-provider-for-wordpress/29934/9 "2016-10-05T19:49:16Z")

</div>

Using Discourse as an SSO provider is documented here:

> [@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 …

That howto also links to a PHP script by @paxmanchris that implements Discourse as SSO provider:

> <https://gist.github.com/paxmanchris/e93018a3e8fbdfced039>

---

_[View the full topic](https://meta.discourse.org/t/discourse-a-sso-provider-for-wordpress/29934)._