You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@guacamole.apache.org by "Marco (Jira)" <ji...@apache.org> on 2026/03/18 12:50:00 UTC

[jira] [Commented] (GUACAMOLE-361) CAS global logout

    [ https://issues.apache.org/jira/browse/GUACAMOLE-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18066565#comment-18066565 ] 

Marco commented on GUACAMOLE-361:
---------------------------------

That would be really great to have! We use Keycloak and we would like on logoff for all tokens to become invalid, both for the session and guacamole itself.

I see, that on connecting, the api endpoint is called to get a token. Does this token ever become invalid? Is it becoming invalid when logging off? Is it becoming invalid when requesting a new token?

> CAS global logout
> -----------------
>
>                 Key: GUACAMOLE-361
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-361
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole-auth-sso-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.20.10#820010)