[
https://issues.apache.org/jira/browse/GUACAMOLE-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889349#comment-17889349
]
Nick Couchman commented on GUACAMOLE-1401:
------------------------------------------
I suspect this has to do with the container linking, which is deprecated and
should not be used. These issues should also be largely resolved by changes
that are part of GUACAMOLE-374.
> 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.20.10#820010)
