תוסף אימות מותאם אישית מבקש ממשתמשים קיימים ליצור חשבון חדש לאחר אימות

סיכום מבוסס בינה מלאכותית

kwakubonsam reports that after upgrading their Discourse forum to V3, some users authenticated via their company’s SSO are incorrectly prompted to create a new account — even though their accounts already exist. These users can regain access by resetting their passwords. The issue is inconsistent, affecting only some users, making debugging difficult. pfaffman asks whether the affected users have mismatched email addresses compared to their existing accounts and inquires about the plugin’s authentication mechanism, noting that Discourse Connect typically eliminates local passwords. kwakubonsam confirms the emails match and shares the plugin’s GitHub repository: discourse-purecloud-auth-plugin, inviting further questions about the code. The core mystery remains: why SSO-authenticated users are being treated as new registrants despite having pre-existing accounts.

We recently upgraded our forum to V3. Before doing so, I tested our plugin in a local instance and realized that our auth plugin does not work with V3 so I made the necessary changes to make it work before upgrading the forum on prod. After the upgrade, some users get asked to create a new account after getting authenticated with my company’s SSO. The weird thing is their accounts already exist and they can get back in by resetting their passwords. I am finding it hard to debug the issue because not all users face this problem and I cannot find the root source of the issue. Does anyone have an idea why this is happening?

Do they have different email addresses than they have for their existing accounts?

How does your auth plugin work? If it were discourse connect then there would be no local passwords. Maybe share a link to the plugin.

No, they have the same email.

Here is the link to the plugin: GitHub - purecloudlabs/discourse-purecloud-auth-plugin · GitHub

Please let me know if you have any questions about the code. Thank you!