# Email activation when using SSO

**URL:** <https://meta.discourse.org/t/email-activation-when-using-sso/28861>\
**Category:** Feature\
**Tags:** sso, approval, discourseconnect\
**Created:** [5월 15, 2015, 2:28오후 UTC](https://meta.discourse.org/t/email-activation-when-using-sso/28861 "2015-05-15T14:28:11Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![tobiaseigen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tobiaseigen/32/539204_2.png) [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)\
**Post date:** [5월 19, 2015, 2:52오후 UTC](https://meta.discourse.org/t/email-activation-when-using-sso/28861/11 "2015-05-19T14:52:29Z")

</div>

This conversation reminds me of another one - discourse is doing so much better at all of this and is getting better all the time, while other platforms (like wordpress) are not keeping with the times. So it may be worthwhile to make it easier to use discourse as the SSO source.. as part of the wp-discourse wordpress plugin, for example.

[https://meta.discourse.org/t/discourse-as-sso-source-of-authority-for-wordpress/18400](https://meta.discourse.org/t/discourse-as-sso-source-of-authority-for-wordpress/18400)

But this idea of @plkap74 is also very interesting - why not just still keep that layer of validation in discourse so when the user comes over from the other site they can be verified again. Perhaps we could then also still benefit from other discourse features that we lose with SSO, like the invites system, which I sorely miss!

---

_[View the full topic](https://meta.discourse.org/t/email-activation-when-using-sso/28861)._