You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Edwin Mackenzie-Owen (Jira)" <ji...@apache.org> on 2021/08/18 14:14:00 UTC

[jira] [Updated] (GUACAMOLE-1401) Docker/guacamole-client: MySQL auth fails when MYSQL_PORT not set

     [ https://issues.apache.org/jira/browse/GUACAMOLE-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Edwin Mackenzie-Owen updated GUACAMOLE-1401:
--------------------------------------------
    Description: 
Hi,

I was trying to set up Guacamole in Kubernetes using both LDAP and MySQL. LDAP users could log in, but {{guacadmin}} could not. Manually assigning admin permissions to a LDAP  user via MySQL commands also wouldn't work. I suspected the MySQL connection was not working.

So I looked at the {{guacamole.properties}} inside the guacamole container. It contained the line: {{mysql-port: tcp://<resolved-address-of-mysql-hostname>:3306. }}

I had not set the environment variable {{MYSQL_PORT}}, because the manual says it defaults to 3306. After I set {{MYSQL_PORT}} to {{3306}}, the line in {{guacamole.properties}} changed to {{mysql-port: 3306}}, and I could log in as {{guacadmin}}.
h4. Additional information:

I used {{guacamole/guacamole:*1.3.0.*}} as it was not clear whether the {{latest}} tag would provide a recent build of 1.3.0 or a development version.

  was:
Hi,

I was trying to set up Guacamole in Kubernetes using both LDAP and MySQL. LDAP users could log in, but {{guacadmin}} could not. Manually assigning admin permissions to LDAP via MySQL commands also wouldn't work. I suspected the MySQL connection was not working.

So I looked at the {{guacamole.properties}} inside the guacamole container. It contained the line: {{mysql-port: tcp://<resolved-address-of-mysql-hostname>:3306. }}

I had not set the environment variable {{MYSQL_PORT}}, because the manual says it defaults to 3306. After I set {{MYSQL_PORT}} to {{3306}}, the line in {{guacamole.properties}} changed to {{mysql-port: 3306}}, and I could log in as {{guacadmin}}.
h4. Additional information:

I used {{guacamole/guacamole:*1.3.0.*}} as it was not clear whether the {{latest}} tag would provide a recent build of 1.3.0 or a development version.


> Docker/guacamole-client: MySQL auth fails when MYSQL_PORT not set
> -----------------------------------------------------------------
>
>                 Key: GUACAMOLE-1401
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1401
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole-auth-jdbc-mysql
>    Affects Versions: 1.3.0
>            Reporter: Edwin Mackenzie-Owen
>            Priority: Trivial
>              Labels: Docker
>
> Hi,
> I was trying to set up Guacamole in Kubernetes using both LDAP and MySQL. LDAP users could log in, but {{guacadmin}} could not. Manually assigning admin permissions to a LDAP  user via MySQL commands also wouldn't work. I suspected the MySQL connection was not working.
> So I looked at the {{guacamole.properties}} inside the guacamole container. It contained the line: {{mysql-port: tcp://<resolved-address-of-mysql-hostname>:3306. }}
> I had not set the environment variable {{MYSQL_PORT}}, because the manual says it defaults to 3306. After I set {{MYSQL_PORT}} to {{3306}}, the line in {{guacamole.properties}} changed to {{mysql-port: 3306}}, and I could log in as {{guacadmin}}.
> h4. Additional information:
> I used {{guacamole/guacamole:*1.3.0.*}} as it was not clear whether the {{latest}} tag would provide a recent build of 1.3.0 or a development version.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)