guacamole-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (GUACAMOLE-41) Document how to use LDAP with Docker
Date Tue, 31 May 2016 07:14:13 GMT


ASF GitHub Bot commented on GUACAMOLE-41:

Github user mike-jumper commented on a diff in the pull request:
    --- Diff: guacamole-docker/ ---
    @@ -115,6 +119,35 @@ The process for doing this via the `mysql` utility included with
MySQL is
     documented in
     [the Guacamole manual](
    +Deploying Aoache Guacamole with LDAP authentication
    +    docker run --name some-guacamole --link some-guacd:guacd    \
    +        -e LDAP_HOSTNAME=                            \
    +        -e LDAP_USER_BASE_DN=ou=people,dc=example,dc=com        \
    +        -e LDAP_CONFIG_BASE_DN=ou=connections,dc=example,dc=com \
    +        -d -p 8080:8080 glyptodon/guacamole
    +Linking Guacamole to your LDAP directory will require additional configuration parameters
    +specified via environment variables. These variables collectively describe how Guacamole
    +will connect to LDAP:
    +1. `LDAP_HOSTNAME` - The base of the DN for all Guacamole users.
    --- End diff --
    Nope. Copy/paste error, I assume?

> Document how to use LDAP with Docker
> ------------------------------------
>                 Key: GUACAMOLE-41
>                 URL:
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole-docker
>    Affects Versions: 0.9.9
>            Reporter: James Johnston
> As part of GUAC-1467 on the Glyptodon JIRA, the Docker image for guacamole was improved
to allow specification of LDAP authentication parameters. However, as an end-user, there is
no way for me to even know this functionality is available because it is not documented at
all. It appears to be undocumented.
> I think the at
should be updated with information about how to use LDAP authentication, so that people can
use this new feature. :)

This message was sent by Atlassian JIRA

View raw message