# Use Discourse as an identity provider (SSO, DiscourseConnect)

**URL:** <https://meta.discourse.org/t/use-discourse-as-an-identity-provider-sso-discourseconnect/32974>\
**Category:** Integrations\
**Tags:** sso, discourseconnect, how-to\
**Created:** [September 7, 2015, 9:19am UTC](https://meta.discourse.org/t/use-discourse-as-an-identity-provider-sso-discourseconnect/32974 "2015-09-07T09:19:21Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![ianmackinnon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ianmackinnon/32/102985_2.png) [@ianmackinnon](https://meta.discourse.org/u/ianmackinnon)\
**Post date:** [March 12, 2016, 1:11am UTC](https://meta.discourse.org/t/use-discourse-as-an-identity-provider-sso-discourseconnect/32974/5 "2016-03-12T01:11:28Z")

</div>

> [@techAPJ](#):
>
> Compute the HMAC-SHA256 of sso using sso\_secret as your key.

`sso` seems to have a trailing newline which needs to be included when sent to the HMAC function, so it’s important to make sure that SSO consumer applications don’t strip whitespace from these query arguments.

---

_[View the full topic](https://meta.discourse.org/t/use-discourse-as-an-identity-provider-sso-discourseconnect/32974)._