# Email activation when using SSO

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

<div class="post-metadata">

**Author:** ![purldator](https://avatars.discourse-cdn.com/v4/letter/p/bcef8e/32.png) [@purldator](https://meta.discourse.org/u/purldator)\
**Post date:** [May 17, 2015, 6:20am UTC](https://meta.discourse.org/t/email-activation-when-using-sso/28861/6 "2015-05-17T06:20:58Z")

</div>

I disagree. A second layer of protection doesn’t hurt. This is especially true if it’s a _Human_ spammer that uses a well-known spam domain, IP, ect.

But for those who don’t want the extra barrier, a configurable option would make more sense.

> [@nahtnam](#):
>
> It should be the third party sites job to verify the email and have spam protection, not discourse’s.

Basically, I would trust someone else as far as I can throw 'em, or be able to make dummy accounts on their network.

---

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