[
https://issues.apache.org/jira/browse/GUACAMOLE-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16985458#comment-16985458
]
Stewart Alpert commented on GUACAMOLE-361:
------------------------------------------
I took a stab at writing such a logout today and ran into a snag, which I'm
guessing GUACAMOLE-680 will try to address. I wrote a controller that deletes
GUAC's localstorage objects, redirects to the CAS logout endpoint, and gets
called when CASAuthenticatedUser.invalidated() is called. For users who get
the connections menu portion of the app, this logout works fine. For a user
with, for example a single RDP connection who eventually gets to the
"DISCONNECT" dialog and chooses the Logout button...my endpoint is called, but
it appears the browser has already been redirected (looks like it goes to "/")
and begins to login (i.e. redirect to CAS) before I can log it out. I'm
guessing I'm blocked until GUACAMOLE-680 is done, unless anyone can point me in
a direction I haven't considered...
> CAS global logout
> -----------------
>
> Key: GUACAMOLE-361
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-361
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-auth-cas
> Reporter: Nicklas Björk
> Priority: Minor
>
> It would be nice to have a configurable single sign-out option available when
> using CAS as the authentication method. For example to direct the Logout
> option in the menu to the CAS logout endpoint, to make sure that the
> Guacamole session, as well as the CAS session, are both ended.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
