I’m helping with an instance with wp-discourse and a day or to ago (I think when they upgraded to beta6) SSO logins started to fail. They seem to be failing with {:primary_email=>"has already been taken"} so somehow it’s not connecting existing accounts correctly? Verbose SSO log: Record was inva…

There haven’t been any recent changes to the WP Discourse SSO login code. If manually creating the SSO record is fixing the issue, then the problem seems to be that the user IDs that are being sent from WordPress as the external_id don’t match the external IDs on the user’s Discourse SSO record. Th…

Strange. Is that activation in function.php or in the wp-discourse web interface? (If the site weren’t down (to logins) I’d rtfm).

Oh, are you using Discourse as the SSO provider? Or WP as the SSO provider? (I was assuming the latter)

WP is SSO provider. . . . My suspicion was the new security thing (that I can’t quite remember what it was now) caused the problem. They had http:// rather than https:// for the SSO_URL, even though the site was https (and I guess redirecting to https so it still worked). But that doesn’t seem to m…

[image] pfaffman: external_id: 16719 Does this user exist in the database? SingleSignOnRecord.where(external_id: 16719) How about a user with your email? User.find_by_email("jay@literatecomputing.com")

No. I checked a couple (of the SingleSignOnRecords)and it seems that they aren’t getting created? (Users are fine and created) I tried creating a new user, as I was concerned that it might actually be true that I’d created a user on the discourse side that was causing a problem. Looks like the las…

So it looks like the user is getting created, but it’s failing when it tries to create the SSO Record? Hey, this looks strange: {"admin"=>false, "moderator"=>false, "locale"=>nil, "name"=>"Jay Pfaffman", "title"=>nil, "username"=>"pfaffman-test21"} username there is pfaffman-test21 but username i…

[image] pfaffman: Strange. Is that activation in function.php or in the wp-discourse web interface? The require_activation parameter is set by the WP Discourse plugin if a site isn’t using the default WordPress registration system. When it is set, WordPress users are not matched to Discourse …

OK. Manually creating the SignleSignOnRecord makes the login work. It does seem clear that something changed on the WP side? [image] simon: The require_activation parameter is set by the WP Discourse plugin if a site isn’t using the default WordPress registration system. And that’s been the…

Thanks very much. I did a couple searches for require_activation and couldn’t find the “how to turn off…”. When the sun comes up in WordPress guys side of the world hopefully they can resolve this. I don’t know whether the registration system changed recently and the site owner doesn’t seem to know…

Trouble with wp-discourse logins

Product Support WordPress

david (David Taylor) March 29, 2019, 4:03pm 2

Matching up by email will never happen if you have require_activation: true. I don’t think anything has changed on the Discourse side recently… the last change to that logic was 7 months ago.

Topic		Replies	Views
Imported user unable to log in if no SSO details in Discourse WordPress sso , discourseconnect	3	1037	March 18, 2019
DiscourseConnect SSO error WordPress	3	761	August 9, 2021
Merging existing Discourse and WP user lists WordPress	37	3728	May 28, 2019
Setup DiscourseConnect - Official Single-Sign-On for Discourse (sso) Integrations sso , discourseconnect , configuring , how-to	46	461280	May 27, 2026
Wp-discourse getting odd data from wp - debug help? WordPress	2	1235	December 19, 2018

Trouble with wp-discourse logins

Related topics