The solution was to add below property in cas.properties file *cas.ticket.tgt.onlyTrackMostRecentSession=false* On Monday, 15 February 2021 at 11:45:14 UTC+5:30 nandini s wrote:
> Hi Team, > > We are on version 5.2.4 of CAS for our applications. We have a case where > single logout is not working. Below is the description: > > I open a browser window and login to my application through CAS(Tab 1). I > open the same application in the same browser window but different > tab(Tab2). > > - When i logout from the application in Tab1, the Tab2 sessionId (ST > ticket) is invalidated, which is correct behavior. > - When i logout from the application in Tab2, the Tab1 sessionId is > still valid and I am able to proceed with the session operations. - This > is > the issue we are facing with SLO. > - However, the refresh of the Tab1, will take me login session > > These are the CAS properties w.r.t the logout and SLO: > ############## Logout ############### > cas.logout.followServiceRedirects=false > cas.logout.redirectParameter=service > cas.logout.confirmLogout=false > ############# Single Logout ############ > cas.slo.disabled=false > cas.slo.asynchronous=true > > I use /serviceValidate endpoint of the CAS to validate the serviceTicket. > -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- 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/bc95cc80-cbd0-4176-bdff-00f31a3cdfe9n%40apereo.org.
