Ankur, You could create a filter and place it before the logout filter in web.xml.
Ray On Mon, 2017-04-24 at 05:40 -0700, Ankur Verma wrote: I have successfully configured and implemented the SSO + SLO using following artifacts: Cas Server 4.1 java client 3.1 ticket authentication and validation protocol- cas2.0 Logout type- backchannel the problem is that , even after SLO , client is not getting any message of the logout , and whenever a request to a protected resource happens , the client redirects to the cas authentication page. This flow fails when client has input significant amount of information on he UI of another tab(request) in the same session , and instead of a message ( prompt telling user that his session has been logged out ), but instead he just pushes a button say submit. and voila , the request is redirected to authentication post logout from another application and all his data that he meticulously feeded in the form will be lost. What i understand is there is already a listened in configuring single logout configuration , constantly looking for the SLO event , but how to attach a prompt with it to send some reasonable message to the user so that he can atleast have another options before hitting the save button. Please help me. Thanks! -- Ray Bon Programmer analyst Development Services, University Systems 2507128831 | CLE 023 | [email protected] -- - CAS gitter chatroom: https://gitter.im/apereo/cas - CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html - CAS documentation website: https://apereo.github.io/cas - CAS project website: https://github.com/apereo/cas --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/1493055846.25318.14.camel%40uvic.ca.
