# DiscourseConnect SSO error

**URL:** https://meta.discourse.org/t/discourseconnect-sso-error/199390
**Category:** WordPress
**Created:** [August 6, 2021, 1:45am UTC](https://meta.discourse.org/t/discourseconnect-sso-error/199390 "2021-08-06T01:45:35Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![jakelunniss](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jakelunniss/32/194661_2.png) [@jakelunniss](https://meta.discourse.org/u/jakelunniss)
#### Post date: [August 6, 2021, 1:45am UTC](https://meta.discourse.org/t/discourseconnect-sso-error/199390/1 "2021-08-06T01:45:35Z")

</div>

Hey Brains Trust!

I have a problem with the SSO.

An existing user who has been authenticated and was previously able to login now gets this message when attempting to access the forum:

 ![image](https://global.discourse-cdn.com/meta/original/3X/4/c/4c58ac753b76447f6b1aa11c69dcc1384b77d67f.png)

Here’s his SSO details:

 ![image](https://global.discourse-cdn.com/meta/original/3X/b/8/b802fde25795c38de9acf424dbe00e9f3c97a4b1.png)

I am able to impersonate his user, but cannot login via wordpress.

In the error logs, this is the error:

 ![image](https://global.discourse-cdn.com/meta/original/3X/0/0/00f11ca06253b8760d0bcfb5969b0897c56ae0b8.png)

I have no idea why. Over to you wonderful intelligent people!

---

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [August 6, 2021, 2:30am UTC](https://meta.discourse.org/t/discourseconnect-sso-error/199390/2 "2021-08-06T02:30:51Z")

</div>

Hey @jakelunniss,

The error in Discourse logs seems to be related to another user (note the `name` attribute).

As for the user who’s unable to log-in, I suspect the issue is that `require_activation` is set to `true` in the SSO payload. This prompts Discourse to try and create a new user instead of looking up an existing one. As his account already exists, the error is thrown.

There might be a few reasons why `require_activation` is true for an existing user, however could you go to the user’s Wordpress profile, check this box and click “Update Profile”

![Screen Shot 2021-08-06 at 10.27.53 AM](https://global.discourse-cdn.com/meta/optimized/3X/4/e/4e7e035fd86030b10876c3ba5c504dcc33c5c109_2_690x34.png)

Then ask him to attempt to login again.

(I’m assuming here you don’t have any custom code on your Wordpress which uses the filter `discourse_email_verification`)

p.s. I would recommend obscuring the email addresses in the screenshots (data privacy etc.)

---

<div class="post-metadata">

### Author: ![jakelunniss](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jakelunniss/32/194661_2.png) [@jakelunniss](https://meta.discourse.org/u/jakelunniss)
#### Post date: [August 8, 2021, 5:49am UTC](https://meta.discourse.org/t/discourseconnect-sso-error/199390/3 "2021-08-08T05:49:26Z")

</div>

Hey @angus

Thanks for replying!

Firstly, the email address - Johnathan is a friend of mine. His email address is visible on his website and he doesn’t give two poops about privacy. Otherwise I would have obscured it.

I checked the email address verified on his profile and it was already checked.

I unchecked this:

![image](https://global.discourse-cdn.com/meta/original/3X/3/c/3ca1ebbf321baf68e202346c58c99a02734a9fa6.png)

And that seems to have resolved the problem.

No, there’s no custom code using the filter `discorse_email_verification`

The issue has popped up for another user today so I’d still like to get to the bottom of it, as we’d prefer that users can’t change their email address in discourse.

Thanks again!

---

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [August 9, 2021, 1:33am UTC](https://meta.discourse.org/t/discourseconnect-sso-error/199390/4 "2021-08-09T01:33:27Z")

</div>

Did he change his email recently, or is the log screenshot of an error from a different user?
