You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are having an issue after we have upgraded our CKAN from 2.9.5 to 2.9.8 and saml2auth from 1.2.2 to 1.2.3/1.3.0.
Upon clicking Logout from a SSO login, it will send a request to the client SSO page and redirect to /slo once done. However, it keeps looping back to the client SSO page when redirected back to /slo which redirect to user/_logout
Looking at the cookies, it seems like there are 2 cookeis for auth_tkt and it only clear one of them which keeps gettting in the loop.
We tried to add one code within _perform_slo(): after subject_id = get_subject_id(session) to ensure that the subject_id is none and it got out of the loop.
session.clear()
Can you please advise if this is a bug or this should be handle by CKAN core but somehow was called properly when logging out via SSO?
Thanks
The text was updated successfully, but these errors were encountered:
COGTeamGDMP
changed the title
Infinite Loop when logout of CKAN
[BUG]Infinite Loop when logout of CKAN
Apr 14, 2023
We are having an issue after we have upgraded our CKAN from 2.9.5 to 2.9.8 and saml2auth from 1.2.2 to 1.2.3/1.3.0.
Upon clicking Logout from a SSO login, it will send a request to the client SSO page and redirect to /slo once done. However, it keeps looping back to the client SSO page when redirected back to /slo which redirect to user/_logout
Looking at the cookies, it seems like there are 2 cookeis for auth_tkt and it only clear one of them which keeps gettting in the loop.
We tried to add one code within _perform_slo(): after subject_id = get_subject_id(session) to ensure that the subject_id is none and it got out of the loop.
session.clear()
Can you please advise if this is a bug or this should be handle by CKAN core but somehow was called properly when logging out via SSO?
Thanks
The text was updated successfully, but these errors were encountered: