[
https://issues.apache.org/jira/browse/GUACAMOLE-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17224955#comment-17224955
]
Nick Couchman commented on GUACAMOLE-519:
-----------------------------------------
[~Ghost_Knight]:
Sounds good. See:
https://github.com/apache/guacamole-client/blob/9ab3e854ab4bb92913576f58cdb2657dc7c25df0/guacamole/src/main/webapp/app/auth/service/authenticationService.js#L278-L302
Also, we had some discussion about re-arranging some things related to logout
to better handle these scenarios so that you can both delete the Guacamole
token, invalidating the Guacamole Login, and then also call an external URL to
potentially invalidate some upstream login. This was handled via GUACAMOLE-680
- PR (sorely lacking any attention) is here:
https://github.com/apache/guacamole-client/pull/346
> Implement Single Logout on OpenID Extension
> -------------------------------------------
>
> Key: GUACAMOLE-519
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-519
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-auth-openid
> Environment: Ubuntu 16.04
> Tomcat 8
> Reporter: Kevin Chan
> Priority: Minor
>
> Currently when using OpenID Connect for authentication, when a user uses the
> logout link, they get re-authenticated and logged back in.
> Would like to override the logout to send an SLO and/or redirect user to a
> different site.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
