(Note, this was also reported here: Connection lost during callback · Issue #28 · habi-dat/discoursesso · GitHub) Hello, we are having a very weird issue with our Discourse SSO. Ever since one user logged out of impersonation, he is unable to log back in. This is what happens now if he tries to log in: (the user was logged into Nextcloud previously). [grafik] The Server just closes the connection. I am unable to find any error log. Not inside any of the nginx proxies, not inside Discourse, not inside Nextcloud. Interestingly it has nothing to do with the network or device. It is just this user that fails to log in. I also tried clearing out the SSO Data from Discourse, changed the Email Address to force creation of a new Discourse Account. The Problem still persists. I suspect this is an issue with the Nextcloud plugin, however I don’t see any error messages by Discourse, which surprises me. (I cleared the log and tried again, no record appeared.)

I just did. The only record is: Verbose SSO log: Started SSO process add_groups: admin: moderator: avatar_force_update: avatar_url: bio: card_background_url: confirmed_2fa: email: external_id: groups: locale: locale_force_update: location: logout: name: no_2fa_methods: nonce: profile_background_url: remove_groups: require_2fa: require_activation: return_sso_url: https://hub.diehumanisten.de/session/sso_login suppress_welcome_message: title: username: website:

Is this issue still ongoing @simon.michalke?

yes, we just tested it again and it still persists.

Okay, now we have a REAL issue. The problem seems to be spreading to other user. And the second one is not an admin and can therefore not use the workaround. If I want to contact (paid) support, who should I talk to in my case?

Was this the right answer to your issue in the end? :crossed_fingers: [image][Paid] Help with fixing SSO issue OR adapting (simplifying) SAML Plugin I think I found the issue: Yahoo login for Discourse - #13 by pfaffman closing this for now.

Yes. Nextcloud SSO only supports GET and not POST-based login. Our nginx proxy silently dropped the request since we had too many groups filling up the request header. Our current workaround is manually patching the Plugin to not include groups: https://github.com/soudis/discoursesso/issues/28#issuecomment-1165819892 We will switch to keycloak for authentication soon.

SSO Callback closes connection (0 bytes sent by server); used logged out of impersonation previously

Product Support SSO

RGJ (Richard - Communiteq) June 5, 2022, 3:00pm 2

Did you enable Admin - Settings - Login - verbose_discourse_connect_logging ?

Topic		Replies	Views
[Paid] Help with fixing SSO issue OR adapting (simplifying) SAML Plugin Marketplace	1	891	June 24, 2022
Users unable to login with Discourse Connect SSO	5	1817	July 8, 2022
I keep getting logged out after implementing Discourse SSO SSO	1	604	June 26, 2023
Issues using SSO in custom web app Development	10	1713	January 9, 2018
SSO gives us an HTTP 419, but works Product Support	1	801	May 21, 2021

SSO Callback closes connection (0 bytes sent by server); used logged out of impersonation previously

Related topics