You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Mike Jumper (Jira)" <ji...@apache.org> on 2020/03/02 02:30:00 UTC

[jira] [Reopened] (GUACAMOLE-758) OpenID Guacamole Logout

     [ https://issues.apache.org/jira/browse/GUACAMOLE-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Jumper reopened GUACAMOLE-758:
-----------------------------------

> OpenID Guacamole Logout
> -----------------------
>
>                 Key: GUACAMOLE-758
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-758
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole-auth-openid
>    Affects Versions: 0.9.14
>         Environment: centos-release-7-5.1804.5.el7.centos.x86_64
>            Reporter: Christopoulos Alexandros
>            Priority: Minor
>             Fix For: 0.9.14
>
>
> I have a configuration that has Keycloak and Guacamole. Keycloak is the openID provider. The module I am using for guacamole to connect with Keycloak is guacamole-auth-openid 0.9.14. The login process works fine but whenever I log out from Keycloak client the guacamole session continues to exists. It seems that the logout for Guacamole does not work with the openID extension. There are two scenarios that this is happening:
>  
> 1) I end the session from Keycloak admin and the logout event does not appear to be read by guacamole. After this logout process when redirecting to guacamole application I am still logged in guacamole.
>  
> 2) When logged in with openID in guacamole, once logout button in guacamole is clicked you get logged in again.
>  
> From the above scenarios and by observing the network traffic in the browser it seems that the guacamole openID extension does not handle incoming logout events from openID provider.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)