Hi,
This is another property: the *logoutType* (*BACK_CHANNEL* or
*FRONT_CHANNEL*).
In your case (for the browser to send the logout request), you need the
front channel logout (
https://apereo.github.io/cas/5.3.x/installation/Logout-Single-Signout.html#front-channel
).
Thanks.
Best regards,
Jér
Hi Jérôme,
Thanks for the suggestion, we need the end user's browser to make the
call to the logout URL and I think the URL in the "logoutUrl" value gets
called by the CAS server, no?
- Brian
On 8/7/2018 9:09 AM, Jérôme LELEU wrote:
Hi,
By default, the CAS server will call the service URL
Hi,
By default, the CAS server will call the service URL of the CAS
applications the user has accessed during his SSO session.
But you can change the application logout URL (called by CAS) via the CAS
property when defining the CAS service: logoutUrl.
See: https://apereo.github.io/cas/5.3.x/inst
One of our portal's subapps doesn't get logged out when the portal calls
the /cas/logout URL on our CAS 5.1.2 server, that subapp has it's own
logout URL.
Is there a way within CAS 5 to have the client call a URL in the background
as they log out of a service?
Thanks!
--
- Website: https://aper
