A user, omarfilip, reported an issue where a new SSO user was unexpectedly flagged for approval, and clicking “Approve” triggered a 403 error. The error occurred on Discourse v2.3.0.beta6 +16 and appeared to be related to the combination of SSO and the “invite only” setting — a configuration eviltrout later described as “undefined behavior.” Although the initial error log was client-side JavaScript, eviltrout suspected a server-side issue and asked for further logs, which were unavailable. The issue resolved itself temporarily when omarfilip retried approval, but reoccurred with new users. Further investigation revealed that users imported from phpBB appeared as “Anonymous user from phpBB3,” though this may be unrelated. After omarfilip disabled “invite only,” new SSO users no longer required approval, confirming the root cause. eviltrout committed a fix to prevent enabling “invite only” when SSO is active (commit), and confirmed that the “Share / Invite” modal now correctly restricts email invites when SSO is enabled, addressing omarfilip’s referenced use case. The fix was implemented without requiring a version update.
Perhaps completely unrelated, but… my forum started as an import from phpBB, and all my new users show up as “Anonymous user from phpBB3” even though they are not. For example the user from the OP looks like this:
Okay after looking into it slightly, I suspect the problem here is having SSO + Invite Only was always undefined behavior in Discourse. It doesn’t really make sense to have people log in via SSO but also require an invite.
Is disabling invite only an option for you? Why would you need it enabled?
I looked into this, and it seems to work now. If enable sso is true, the “Share / Invite” (now consolidated) modal does not allow emails, only usernames.