By: Jesús JM user 08 Feb 2021 at 2:01 p.m. CST

4 Responses
Jesús JM gravatar
Hello Gluu Team, I'm experiencing some strange behaviours during SAML Single Logout (SLO). I've configured trust relationships for several services. Single Sign-In seems to work nicely. When it comes to SLO, the user confirms that wants to log out the global session, and after that it seems that the logout has failed for all services. I'm talking about the logout page that starts with the message "Attempting to log out of the following services:", all the entity IDs appear with a red cross indicating that the logout process has failed. However, if I try to access again any of the services involved, it redirects me to the login page. Thus, the session seems to be killed, but these error messages keep showing. I tried to seek for answers in the logs but it seems I'm missing something. Any suggestion will help. Thank you!

By Mobarak Hosen Shakil staff 08 Feb 2021 at 4:24 p.m. CST

Mobarak Hosen Shakil gravatar
Hi Jesús JM, Thanks for reaching out at Gluu. Can you please share screenshots to understand exactly what you're getting? Thanks & Regards ~ Shakil

By Jesús JM user 09 Feb 2021 at 2:41 a.m. CST

Jesús JM gravatar
Hi Shakil, Sure. Here are two screenshots, first with the prompt of Gluu asking to logout, and second with the final result. I'm sharing public google drive links just for the sake that these images don't get lost after a long time. https://drive.google.com/file/d/1iDgM0wmzG8phx0IttiqId6XQXAMomW9O/view?usp=sharing https://drive.google.com/file/d/188bP8DyPd3wxIjK5oJWxLXKBuNxYY_1t/view?usp=sharing Thank you in advance.

By Mobarak Hosen Shakil staff 09 Feb 2021 at 9:11 a.m. CST

Mobarak Hosen Shakil gravatar
Hi, It's a normal scenario. You can customize the `RED cross` logo. Closing this ticket. Thanks & Regards ~ Shakil

By Petr Hroudny user 12 Aug 2021 at 5:01 a.m. CDT

Petr Hroudny gravatar
This is not normal scenario, RED cross means logout failed and the logo should warn user about this. Recent thread at shibboleth-users ML describes similar problem, caused by wrong setting in jetty-rewrite.xml http://shibboleth.net/pipermail/users/2021-August/050718.html