Thanks Nick, The debug log-level have now given me more input on what's causing the error. Apparently it seems like the webapp is still trying to use the default file-based auth mechanism instead of using the mysql/mariadb approach:
17:57:50.495 [http-nio-8080-exec-7] DEBUG o.a.g.a.f.FileAuthenticationProvider - User mapping file "/etc/guacamole/user-mapping.xml" does not exist and will not be read. 17:57:50.500 [http-nio-8080-exec-7] DEBUG o.a.g.r.auth.AuthenticationService - Anonymous authentication attempt from [10.0.0.22, 10.0.0.122] failed. 17:57:50.501 [http-nio-8080-exec-7] DEBUG o.a.g.rest.RESTExceptionMapper - Client request rejected: Permission Denied. 17:58:00.495 [http-nio-8080-exec-2] DEBUG o.a.g.a.f.FileAuthenticationProvider - User mapping file "/etc/guacamole/user-mapping.xml" does not exist and will not be read. 17:58:00.495 [http-nio-8080-exec-2] WARN o.a.g.r.auth.AuthenticationService - Authentication attempt from [10.0.0.22, 10.0.0.122] for user "guacadmin" failed. 17:58:00.495 [http-nio-8080-exec-2] DEBUG o.a.g.rest.RESTExceptionMapper - Client request rejected: Permission Denied. I thought with Version 1.0.0 it was no longer required to specify an authHandler? My /etc/guacamole/guacamole.properties: guacd-hostname: 127.0.0.1 guacd-port: 4822 #MariaDB Settings mysql-hostname: nhmucmasql01.nethavn.net mysql-port: 3306 mysql-database: nhmucrmgw01_nethavn_net mysql-username: nhmucrmgw01_dbuser mysql-password: <redacted> mysql-user-required: true mysql-auto-create-accounts: true mysql-driver: mariadb On Tue, Aug 31, 2021 at 5:49 PM Nick Couchman <vn...@apache.org> wrote: > On Tue, Aug 31, 2021 at 11:46 AM Alexander Pelz <al...@nethavn.com> wrote: > >> I actually have both on the system installed. The MySQL connector via the >> .deb package it came with and the mariadb connector using the libs folder >> in /etc/guacamole. >> However even after specifying the driver parameter and restarting guacd >> and tomcat there is still no change in login. >> >> 31-Aug-2021 17:43:27.589 INFO [main] >> org.apache.catalina.startup.Catalina.start Server startup in [2433] >> milliseconds >> 17:43:27.793 [http-nio-8080-exec-5] WARN >> o.a.g.e.AuthenticationProviderFacade - Authentication attempt ignored >> because the relevant authentication provider could not be loaded. Please >> check for errors earlier in the logs. >> 17:43:27.794 [http-nio-8080-exec-5] WARN >> o.a.g.e.AuthenticationProviderFacade - Authentication attempt ignored >> because the relevant authentication provider could not be loaded. Please >> check for errors earlier in the logs. >> 17:43:31.033 [http-nio-8080-exec-2] WARN >> o.a.g.e.AuthenticationProviderFacade - Authentication attempt ignored >> because the relevant authentication provider could not be loaded. Please >> check for errors earlier in the logs. >> 17:43:31.033 [http-nio-8080-exec-2] WARN >> o.a.g.e.AuthenticationProviderFacade - Authentication attempt ignored >> because the relevant authentication provider could not be loaded. Please >> check for errors earlier in the logs. >> 17:43:31.034 [http-nio-8080-exec-2] WARN >> o.a.g.r.auth.AuthenticationService - Authentication attempt from >> [10.0.0.22, 10.0.0.122] for user "guacadmin" failed. >> >> >> >> >> Guac presents the standard "invalid login" msg: >> [image: image.png] >> >> To be sure I have removed all entries for ldap in the .properties and >> also moved the extensions module for ldap away to be sure it isn't that. >> Any other hints? >> >> > A few things to check: > * Make sure you're using the same version of Guacamole Client (the WAR) > and the authentication extensions. > * Bump up logging in the web application to see if it generates anything > more useful: > http://guacamole.apache.org/doc/gug/configuring-guacamole.html#webapp-logging > > -Nick > >>