Hi Paul,
I am also agreeing with you that logout with CAS doesn't mean logout Google
account / other 3rd party account. However I don't spot such issue in my
implementation.
I am using Google Delegated Authentication as well, I am using CAS 6.2.6.
No such issue spotted. Maybe you should try u
Hey denizg,
first thanks for you suggestion. But I actually want SLO. I want to destroy
the SSO session and not only the application session. I also configured
front channel to make it work.
No, the problem is something different: If I use delegated SSO provider
like Google or GitHub to authen
edit: single sign on out
dyte gyte , 24 Ağu 2020 Pzt, 11:46 tarihinde şunu
yazdı:
> Hello,
>
> afaik, there are 2 logout type: single logout and single sign-on. the
> default behavior is single logout which means that if you logout current
> app, you also logout all applications that cas is conn
Hello,
afaik, there are 2 logout type: single logout and single sign-on. the
default behavior is single logout which means that if you logout current
app, you also logout all applications that cas is connected. this is the
situation you are facing. but you need single sign on as i understand.
basi
Hey guys,
we noticed some new behavior with delegated SSO authentication. When I
login with my Google SSO account at our CAS and logout again, I am not only
logged out from CAS but also from my Google account. This also happens with
delegated GitHub SSO.
We are using CAS 6.2.1 but I am unsure
