Not the case – we have a pretty vanilla implementation of what’s described in Setup DiscourseConnect - Official Single-Sign-On for Discourse (sso) by following the redirects. It has been working smoothly for a few years and we haven’t touched it.
While we are not doing any unusual SSO things, I did try that anyway by disabling it in the Rails console and all it did for me was remove the error message, in the sense that when the SSO provider redirected back to Discourse, instead of the Account login timed out, please try logging in again. error, there was no message at all (error or otherwise) – but, unfortunately, still logged out.
I’m also grasping for straws here as this is quite odd. I think the fact that the issue didn’t show up when we initially updated to 3.3.3 via the the web interface but only (~36h) later after a console rebuild may be a clue, but I don’t know enough about the differences between the two.
I have tried upping again to 3.3.3 and the issue returned immediately. Switching back to 3.3.2 made SSO work again.