It needs idToken in id_token_hint url parameters) that contains clientId, it can be the same id token that be retrieved in login process. On Thursday, November 9, 2023 at 4:20:04 PM UTC+3:30 Udo Einspanier wrote:
> Hi, > > we have CAS 6.6 as OIDC provider. When our client initiates logout, it > goes to https://.../cas/oidc/oidcLogout?post_logout_redirect_uri=https:/... > > In the YAML configuration we have: > > cas: > logout: > followServiceRedirects: true > removeDescendantTickets: true > > I would expect CAS to redirect to the URL in parameter > post_logout_redirect_uri, but instead > shows a logout page titled "Logout successful" where the user can click on > the logout URL > specified in the logout request. > Is there some additional setting required for OIDC, or are we missing > something to allow automatic > redirect without user interaction? > > Thanks and best regards, > Udo > > > -- - 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/6b3915e9-907f-4a6f-a82a-ec99ef999458n%40apereo.org.
