You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Stu B (Jira)" <ji...@apache.org> on 2022/03/29 12:23:00 UTC

[jira] [Commented] (GUACAMOLE-1569) SAML Extension handling missing from start.sh

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

Stu B commented on GUACAMOLE-1569:
----------------------------------

I've just read through the [original pull request comments|https://github.com/apache/guacamole-client/pull/615] and can see that this is likely going to be in the 1.5.0 release. I expect that this bug can be closed as it isn't actually a bug.

> SAML Extension handling missing from start.sh
> ---------------------------------------------
>
>                 Key: GUACAMOLE-1569
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1569
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole-docker
>    Affects Versions: 1.4.0
>         Environment: Docker
>            Reporter: Stu B
>            Priority: Major
>
> I've been trying to get the SAML extension working correctly in the latest 1.4.0 docker containers.
> I've found that the start.sh script used to validate SAML parameters and load the SAML extension in the 1.4.0 release is incomplete. It looks like the update to this script was after the 1.4.0 release?
> [https://github.com/apache/guacamole-client/blob/1.4.0/guacamole-docker/bin/start.sh]
> The updated script to properly handle the SAML extension with Docker environment variables is in Master:
> [https://github.com/apache/guacamole-client/blob/master/guacamole-docker/bin/start.sh]
> This means that the image on dockerhub is not able to use the SAML extension when the properties are defined via docker environment variables.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)