# Discourse as an SAML, OAUTH IDP?

**URL:** <https://meta.discourse.org/t/discourse-as-an-saml-oauth-idp/29898>\
**Category:** SSO\
**Tags:** discourseconnect\
**Created:** [2015年六月11日 18:05 UTC](https://meta.discourse.org/t/discourse-as-an-saml-oauth-idp/29898 "2015-06-11T18:05:04Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [2016年十一月7日 00:17 UTC](https://meta.discourse.org/t/discourse-as-an-saml-oauth-idp/29898/3 "2016-11-07T00:17:49Z")

</div>

See:

> [@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 is built in, OAUTH2 provider etc would require a custom built plugin, no such plugin exists.

---

_[View the full topic](https://meta.discourse.org/t/discourse-as-an-saml-oauth-idp/29898)._