[GUACAMOLE-1539] "FATAL: No authentication configured" when using the auth-json extension

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Done
• Affects Version/s: 1.4.0
• Fix Version/s: 1.5.0
• Component/s: guacamole-auth-json, guacamole-client
• Assignee: Unassigned
• Reporter: Romain Aviolat
• Created: 17/Feb/22 13:00
• Updated: 31/Aug/22 15:13
• Resolved: 27/Feb/22 22:55

Description

When using Guacamole in "state-less" mode with the auth-json extension, the default setup doesn't work out-of-the-box and complains that a database backend must be present:

| -------------------------------------------------------------------------------
| The Guacamole Docker container needs at least one authentication mechanism in
| order to function, such as a MySQL database, PostgreSQL database, LDAP
| directory or RADIUS server. Please specify at least the MYSQL_DATABASE or
| POSTGRES_DATABASE environment variables, or check Guacamole's Docker
| documentation regarding configuring LDAP and/or custom extensions.
| FATAL: No authentication configured
| -------------------------------------------------------------------------------

The behavior is wrong as Guacamole-client is able to function without any database backend with just the auth-json extension enabled.

By commenting this following condition it works as expected: https://github.com/apache/guacamole-client/blob/master/guacamole-docker/bin/start.sh#L1058

Issue Links

• is duplicated by: GUACAMOLE-1673 Docker Documentaion