# SSO 及上游更改电子邮件地址

**URL:** <https://meta.discourse.org/t/sso-and-changing-email-addresses-upstream/96116>\
**Category:** Product Support\
**Created:** [2018 年8 月 31 日 20:21 UTC](https://meta.discourse.org/t/sso-and-changing-email-addresses-upstream/96116 "2018-08-31T20:21:15Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

作者： ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)\
发布日期： [2018 年8 月 31 日 21:23 UTC](https://meta.discourse.org/t/sso-and-changing-email-addresses-upstream/96116/4 "2018-08-31T21:23:23Z")

</div>

> [@sudoman](#):
>
> Is it dangerous to enable email address overrides if the email addresses are not validated by our authentication server?

If you send the parameter `'require_activation' => 'true'` in the SSO payload after a user changed their email address, Discourse will send the New User activation email to the user. They will need to visit the link in the email before they can log back into their account. The UI for this is a little confusing - it makes it seem that Discourse is creating a new account for the user. Your best approach is to ensure that emails are validated on your authentication server.

> [@sudoman](#):
>
> I wonder whether if there are problems beyond password reset issues if someone supplies an invalid email address to the site, either when first creating an account via SSO or later on.

The big issue is for new users. Supplying an invalid email could cause them to be logged into an existing account. It’s really important to be validating emails on the authenticating site.

---

_[View the full topic](https://meta.discourse.org/t/sso-and-changing-email-addresses-upstream/96116)._
