# \[Paid\] WP + Discourse user authentication for IRC or other chat **URL:** \ **Category:** Marketplace\ **Created:** [2017年四月22日 14:03 UTC](https://meta.discourse.org/t/paid-wp-discourse-user-authentication-for-irc-or-other-chat/61439 "2017-04-22T14:03:39Z")\ **Posts on this page:** 1\ **Showing post:** 6
**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:** [2017年四月23日 15:00 UTC](https://meta.discourse.org/t/paid-wp-discourse-user-authentication-for-irc-or-other-chat/61439/6 "2017-04-23T15:00:39Z")
Ah, you want Discourse to be the parent SSO provider: > [@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 … Yeah, in that case OAuth2 plugins like that Slack plugin don’t matter. And an open source solution like IRC or Mattermost would surely be easier to work with than proprietary chat software, as they’re unlikely to let another application act as the SSO authority. That’s commonly an Enterprise feature. --- _[View the full topic](https://meta.discourse.org/t/paid-wp-discourse-user-authentication-for-irc-or-other-chat/61439)._