Discourse-oauth2-basic Login Inconsistencies

AI-generated summary

Users are experiencing login inconsistencies with the discourse-oauth2-basic plugin paired with Auth0, where previously logged-in users are prompted to create new accounts despite existing accounts being verified. Jim.Morrison reports the issue recurs even after account deactivation and reactivation via email. He has captured a HAR file for analysis and is willing to share it privately. david asks whether accounts are linked by email or Auth0 UID, and whether UIDs may have changed; Jim.Morrison confirms UIDs are unchanged and accounts are UID-linked. Stephen questions if enable local logins was recently enabled, which Jim.Morrison confirms it was not. david offers to review the HAR file and requests verbose server authentication logs for deeper analysis. The team is actively collaborating to resolve the issue, with Jim.Morrison preparing to send the HAR file for further troubleshooting.

We are continuing to run into issues where both employees and customers who have previously successfully logged into our discourse instance in the past is now being prompted to create a new account when they try to login again. I have verified the accounts are present in the system.

If we deactivate the account and send an activation email this gets them logged in for a short period of time until it happens again.

In this latest iteration, I have obtained a HAR file of the login attempt but would need to send that privately (thus not sharing it in the public thread).

We are using the discourse-oauth2-basic paired with Auth0. In the past we have confirmed the data being passed back to Discourse when logging in is correct. Yet it still asks these edge case users to create a new account.

We seriously need help overcoming this hurdle. Please advise, thank you.

How are the accounts supposed to be associated? By email address, or by the UID from Auth0?

Is there any way the UIDs could have changed on Auth0?

If you PM me the HAR file I can take a look, although I can’t promise I’ll be able to solve it with only that. If you have verbose authentication logs from the server that would also be useful.

Has someone recently enabled enable local logins on that instance?

Confirmed no.

UID and there isn’t any modification on them.

I will send this your way and we can build out from there :+1: