Hi there, we have the following setup: Official Discourse 2.5.0 ([ 3f7658cc6e ]) with the discourse-saml plugin (commit 230a58b), Keycloak (10.0.2) as Identity Provider Our Identity Provider is set up to use the url https://discourse.our-domain.xxx/auth/saml/slo as Logout Service POST Binding UR…

We’re not handling the saml_uid session value in our plugin. It’s handled by the omniauth-saml gem itself. So I’m not sure about why you have an empty value in session["saml_uid"]. You may need to report the issue in omniauth gem. Also, none of the customers have reported an issue in SLO yet.

I have recognized the same thing: 2 applications (discourse and another one. lets name it X) connected to keycloak with SAML. Logout on discourse. The user is also logged out on X and can’t do anything there. Logout on X. The session on keycloak is gone but the user stays online in discourse Even…

Would it be possible to validate if the saml session is still alive? See answer above @vinothkannans

Discourse-saml: SLO가 세션을 취소하지 않음

지원

sbernhard (Bernhard Suttner) 3월 17, 2021, 7:45오전 4

SAML 세션이 여전히 활성 상태인지 검증할 수 있을까요? 위 답변을 참고해 주세요 @vinothkannans

글		댓글	조회수
Discourse SAML logout issue SSO	0	773	11월 25, 2020
IdP-Initiated SLO logout is not working SSO	1	638	9월 18, 2023
Keycloak SSO and logout Support	0	764	1월 28, 2021
SAML is creating error for local user log out SSO	7	865	5월 25, 2023
SAML logout stops working Bug auth-plugins , saml , fixed	3	205	9월 16, 2025

Discourse-saml: SLO가 세션을 취소하지 않음

Related topics