You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@guacamole.apache.org by "Peter Schulz (JIRA)" <ji...@apache.org> on 2017/06/27 08:27:00 UTC
[jira] [Updated] (GUACAMOLE-336) Using extension and config file
resulting in corrupt guacamole.properties entry
[ https://issues.apache.org/jira/browse/GUACAMOLE-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Schulz updated GUACAMOLE-336:
-----------------------------------
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.
{code:none}
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>
{code}
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.
was:
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.
{code:bash}
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>
{code}
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.
> Using extension and config file resulting in corrupt guacamole.properties entry
> -------------------------------------------------------------------------------
>
> Key: GUACAMOLE-336
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-336
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole, guacamole-auth-duo, guacamole-client, guacamole-docker
> Affects Versions: 0.9.12-incubating
> Environment: Official Docker Container & Synology DS415+ (INTEL Atom C2538)
> Reporter: Peter Schulz
> Priority: Minor
> Labels: easyfix
>
> 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.
> {code:none}
> 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>
> {code}
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)