CAS app logout in IDP SLO

[Zico]

Thanks for your valuable insights, Gentlemen.

What I am getting ( I might be wrong ) then.. there is none who actually
made CAS app SLO participation properly work in Shibboleth IDP Production?

On Tue, Mar 3, 2020 at 2:23 PM Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 3/3/20, 2:20 PM, "users on behalf of Michael A Grady" <
> users-bounces at shibboleth.net on behalf of mgrady at unicon.net> wrote:
>
> > It doesn't appear to be back-channel only, it appears to in some cases
> pass a POST back thru the user's browser with a
> > logoutRequest parameter. But it also doesn't seem to be consistent. But
> at least in some cases, it appears to be
> > propagating the logout to participating CAS services thru such a POST
> thru the browser.
>
> Our mechanic for invoking propagation is always done that way to allow the
> UI to report the results, but what happens after that is protocol specific,
> and my understanding is that it's the server hitting an endpoint at the app
> and then tunneling a result back that signals success/failure.
>
> Marvin can correct me of course, but as I understood things, it was just
> what was informally defined for CAS.
>
> -- Scott
>
>
> --
> For Consortium Member technical support, see
> https://wiki.shibboleth.net/confluence/x/coFAAg
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>


-- 
Best,
Zico
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20200304/19163064/attachment.html>