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

ASF GitHub Bot commented on GUACAMOLE-41:
-----------------------------------------

Github user jmuehlner commented on a diff in the pull request:

    
https://github.com/apache/incubator-guacamole-client/pull/11#discussion_r65219302
  
    --- Diff: guacamole-docker/README.md ---
    @@ -12,8 +12,12 @@ How to use this image
     =====================
     
     Using this image will require an existing, running Docker container with 
the
    -[guacd image](https://registry.hub.docker.com/u/glyptodon/guacd/), and 
another
    -Docker container providing either a PostgreSQL or MySQL database.
    +[guacd image](https://registry.hub.docker.com/u/glyptodon/guacd/), and 
either
    +network access to a working LDAP server, or another Docker container 
providing
    +a PostgreSQL or MySQL database.
    +
    +SQL Based Authentication
    --- End diff --
    
    I added that because the paragraphs below are specific to the SQL 
extensions. I can remove it if it seems confusing.


> Document how to use LDAP with Docker
> ------------------------------------
>
>                 Key: GUACAMOLE-41
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-41
>             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 README.md at 
> https://github.com/glyptodon/guacamole-docker/blob/master/README.md 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
(v6.3.4#6332)

Reply via email to