Hi John, It will use Ajax for frontend call, see this: https://github.com/apereo/cas/blob/master/support/cas-server-support-thymeleaf/src/main/resources/templates/logout/casPropagateLogoutView.html
Note that, due to the recent 3rd party cookie blocking enforced in some of the popular browser, CAS frontend login mechanism have become unreliable if the service do not sure the same domain. I think either use some custom login for logout, or use backend logout is needed if you need cross domain logout (e.g. CAS in www.example1.com, service in www.example2.com). Cheers! - Andy On Tuesday, 25 May 2021 at 01:29:11 UTC+8 john.b...@keap.com wrote: > > Hi all, > > I maintain a CAS server, we have multiple services registered with > different configurations. Some of the services are registered with Front > Channel Logout. I have noticed that CAS will not redirect to the specified > service on logout if one of the Front Channel Logout Services has been > authenticated against. Is this a limitation of the Front Channel Logout > feature or do I have something configured improperly? > > Thanks, > > John > -- - 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 cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/b6eb93b7-71e2-493c-90b2-d5b4a50aca47n%40apereo.org.
