Uploaded image for project: 'Guacamole'
  1. Guacamole
  2. GUACAMOLE-336

Guacamole Docker image may incorrectly concatenate guacamole.properties

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 0.9.11-incubating, 0.9.12-incubating
    • Fix Version/s: None
    • Component/s: guacamole-docker
    • Labels:
      None

      Description

      After setting up guacamole-auth-duo in extension folder it was not possible to make a (rdp) connection anymore. (like: internal server error)
      Logs said that it was not possible to connect to guacd @ 0.0.0.0:80

      A look @ resulting(/merged) config file guacamole.properties showed me, that something is not like it should be.

      root@guacamole-webserver:~# cat .guacamole/guacamole.properties                                       
      duo-integration-key: <my integration key >                                                             
      duo-secret-key: <my secret key>                                              
      duo-api-hostname: <my api hostname>                                                       
      duo-application-key: <my application key>guacd-hostname: 172.17.0.3                                                                            
      guacd-port: 4822                                                                                      
      mysql-hostname: 172.17.0.2                                                                            
      mysql-port: 3306                                                                                      
      mysql-database: guacamole                                                                             
      mysql-username: <mysql user>                                                                           
      mysql-password: <incrediblestrongpassword>
      

      In Line 4 the last line of extension guacamole.properties and first line of existing config are concatinated. Adding an additional line break in the last line of extension config file solves the problem.

      Maybe that is normal behaviour I don't have a strong technical background.

      In the documentation you could be more clear that config files will be merged.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                peschu Peter Schulz
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: