[
https://issues.apache.org/jira/browse/GUACAMOLE-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16179485#comment-16179485
]
Michael Jumper commented on GUACAMOLE-361:
------------------------------------------
I'm not too sure about "overriding" the logout mechanism, but hooking into
logout is certainly an option we should explore. The Guacamole extension system
doesn't currently provide a way for extensions to be informed that the user
session is ending, or that the extension is being unloaded due to server
shutdown. Adding such hooks would allow extensions to cleanup their internals,
if necessary, and would allow the CAS extension to issue a request to the CAS
logout endpoint.
Does CAS provide a logout endpoint that the server could ping when the
Guacamole session is being closed?
> CAS global logout
> -----------------
>
> Key: GUACAMOLE-361
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-361
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-auth-cas, guacamole-client
> Affects Versions: 0.9.13-incubating
> 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
(v6.4.14#64029)
