# עקיפת SSO על ידי הוספת אימייל לא ידוע לקבוצה

**URL:** <https://meta.discourse.org/t/bypass-sso-by-adding-unknown-email-to-group/177339>\
**Category:** Bug\
**Created:** [26 בינואר,‏ 2021,‏ 5:23pm UTC](https://meta.discourse.org/t/bypass-sso-by-adding-unknown-email-to-group/177339 "2021-01-26T17:23:19Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![Grayden\_Shand](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/grayden_shand/32/166586_2.png) [@Grayden\_Shand](https://meta.discourse.org/u/Grayden_Shand)\
**Post date:** [26 בפברואר,‏ 2021,‏ 1:11pm UTC](https://meta.discourse.org/t/bypass-sso-by-adding-unknown-email-to-group/177339/11 "2021-02-26T13:11:42Z")

</div>

> [@tgxworld](#):
>
> When redeeming the invite, the user will have to authenticate via SSO instead of filling up the sign up form. Will that fit your use case?

For our use case, it would be a lot better to be able to suppress the invite emails entirely. For most of our sites (temporary communities for online courses), there is a limited window to sign up (and a fee). So, I imagine someone receiving an invite to the site, who then shows up and sees they can’t actually join anymore, would be frustrated. There’s really no circumstance where we want someone receiving an invite to one of our sites.

If you do go forward with this, I’d ask to also have you implement a warning with something to the effect of: “You are about to email XX people who are not users of your site: [bob@example.com](mailto:bob@example.com), [alice@example.com](mailto:alice@example.com), …” Then we could find those users and remove them from the bulk-add list.

---

_[View the full topic](https://meta.discourse.org/t/bypass-sso-by-adding-unknown-email-to-group/177339)._
