# 用户无法使用 WordPress SSO 登录

**URL:** https://meta.discourse.org/t/users-unable-to-login-using-wordpress-sso/103434
**Category:** WordPress
**Created:** [2018年十二月4日 02:57 UTC](https://meta.discourse.org/t/users-unable-to-login-using-wordpress-sso/103434 "2018-12-04T02:57:53Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)
#### Post date: [2018年十二月4日 19:53 UTC](https://meta.discourse.org/t/users-unable-to-login-using-wordpress-sso/103434/2 "2018-12-04T19:53:12Z")

</div>

> [@samnazarko](#):
>
> I’d have expected the user to be able to make an account with the same email, and be logged in to their existing account. Instead, Discourse seems to be trying to use the username set in Wordpress; rather than the existing Discourse username assigned to that email address.
> 
> Has some behaviour regarding this changed recenttly?

Yes, Discourse recently changed the way it handles SSO login attempts for users with unverified email addresses. If the `require_activation` SSO parameter is set to `true`, users from the SSO provider site are no longer being matched with existing Discourse users by their email address. You can find some details for dealing with this here: [Debug and fixing common DiscourseConnect issues](https://meta.discourse.org/t/debugging-and-fixing-common-sso-issues/103496).

There are a couple of possible solutions for you. If it’s only affecting a few users on your site, you can try the approach that’s outlined in the topic I linked to above. If it’s affecting many users, you may need to add some code to your WordPress site to prevent the `require_activation` parameter from being set to `true`.

How were the users created on your WordPress and Discourse sites? Were users imported into either of them?

---

_[View the full topic](https://meta.discourse.org/t/users-unable-to-login-using-wordpress-sso/103434)._