I have created a Pastebin link with the logs from the tomcat9 start until me trying to log in
- https://pastebin.com/GUd53ahg debug-level loggingshould be enabled as well I hope this helps. Let me know if i can provide anything else. Felix Am Mi., 19. Nov. 2025 um 23:00 Uhr schrieb Michael Jumper < [email protected]>: > On November 19, 2025 1:31:01 PM PST, Vincent Sherwood > <[email protected]> wrote: > >> >> - /extensions: >> - guacamole-auth-jdbc-mysql-1.6.0.jar >> - >> - So i assume i am missing something, correct? and where can i get >> the missing files? >> >> >> Yes. If you use any of the database connectors you must also have the >> jdbc-base jar file too >> >> ------------------------------ >> *From:* Felix Maier <[email protected]> >> *Sent:* Wednesday 19 November 2025 17:33 >> *To:* [email protected] <[email protected]> >> *Subject:* Re: Guacamole 1.6.0 – GUI accessible but login fails / auth >> provider not loading / strange password hash output >> >> You don't often get email from [email protected]. Learn why this >> is important <https://aka.ms/LearnAboutSenderIdentification> >> So the contens of the /lib and /extensions folder are the following: >> >> /lib: >> mysql-connector-j-9.5.0.jar >> >> /extensions: >> guacamole-auth-jdbc-mysql-1.6.0.jar >> >> So i assume i am missing something, correct? and where can i get the >> missing files? >> >> In the future i want to work with ldap but i guess i can add the files >> then right? >> >> Thanks >> Felix >> >> Am Mi., 19. Nov. 2025 um 17:59 Uhr schrieb Vincent Sherwood >> <[email protected]>: >> >> Can you confirm the contents of your GUACAMOLE_HOME (/etc/guacamole >> unless you changed it) sub-directories >> >> /etc/guacamole/lib/ >> mysql-connector-j-9.2.0.jar >> >> /etc/guacamole/extensions/ >> guacamole-auth-jdbc-base-1.6.0.jar >> guacamole-auth-jdbc-mysql-1.6.0.jar >> guacamole-auth-json-1.6.0.jar >> guacamole-auth-ldap-1.6.0.jar >> guacamole-auth-totp-1.6.0.jar >> >> or whatever combination of AUTH jar files you need. >> >> If you are using MariaDB you must have at least the jdbc-base and >> jdbc-mysql jar files in the /extensions/ directory, >> and you must use the mysql connector rather than the mariadb one, and it >> must be in the /lib/ directory >> >> Vincent >> >> ------------------------------ >> *From:* Felix Maier <[email protected]> >> *Sent:* Wednesday 19 November 2025 13:24 >> *To:* [email protected] <[email protected]> >> *Subject:* Guacamole 1.6.0 – GUI accessible but login fails / auth >> provider not loading / strange password hash output >> >> You don't often get email from [email protected]. Learn why this >> is important <https://aka.ms/LearnAboutSenderIdentification> >> >> Hello everyone, >> >> I am currently setting up Apache Guacamole (version 1.6.0) and although I >> can now successfully access the Web GUI, I still cannot log in. I would >> appreciate your help solving this issue. >> >> *Environment details:* >> >> - >> >> Guacamole 1.6.0 >> - >> >> guacd 1.6.0 >> - >> >> Tomcat 9 >> - >> >> MariaDB (external Galera cluster) >> - >> >> MySQL authentication extension >> - >> >> Debian-based Linux >> >> ------------------------------ >> *Issue description* >> >> The GUI loads correctly, and the JDBC driver issue has been resolved. >> However, whenever I try to log in (using *guacadmin*), authentication >> fails. >> >> When I check Tomcat’s status or logs, I consistently see the following >> warnings: >> >> 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. >> WARN o.a.g.event.EventLoggingListener - Authentication attempt from >> 192.168.0.1 for user "guacadmin" failed: unknown error (no specific failure >> recorded) >> >> There are no clear error messages indicating why the authentication >> provider is not being loaded. >> ------------------------------ >> *Strange SQL output* >> >> When I inspect the user table using: >> SELECT * FROM guacamole_user; >> >> I still see strange or binary-like characters in the password_hash and >> password_salt fields. Example: >> >> | password_hash | =�Fp�xe�Զӷ�Ў���i8E�a�x | >> | password_salt | ��J[*m | >> >> I am not sure whether this is expected binary data, an encoding issue, or >> something related to Galera replication. >> ------------------------------ >> *What is working* >> >> - >> >> Database connectivity (after switching to the MariaDB JDBC driver) >> - >> >> Web interface loads normally >> - >> >> Galera cluster is healthy >> - >> >> Schema import completed without visible errors >> >> ------------------------------ >> *My questions* >> >> 1. >> >> Why is the authentication provider not being loaded correctly? >> 2. >> >> Are the binary-looking password hashes normal for Guacamole? >> 3. >> >> Could the Galera cluster setup cause issues with these fields? >> 4. >> >> Is there a recommended way to verify or recreate the default >> *guacadmin* user? >> >> I can provide more logs or configuration details if needed. >> >> Thanks a lot in advance for your help! >> >> Best regards, >> Felix >> >> >> IT Solutions Email Disclaimer - The information contained in this email >> message, including any files transmitted with it, is confidential and may >> be legally privileged. >> >> This e-mail is intended only for the personal attention of the stated >> addressee(s). Any access to this email, including any files transmitted >> with it, by any other person is unauthorised. If you are not an addressee, >> you must not disclose, copy, circulate or in any other way use or rely on >> the accuracy or completeness of the information contained in this email or >> any files transmitted with it. >> >> If you have received this email in error, please inform the sender >> immediately and delete it and all copies from your system. You may not >> forward this email without the permission of the authorised sender. >> >> The views expressed in this email are those of the author, and do not >> necessarily represent the views of IT Solutions or its affiliates. Internet >> communications are not secure and IT Solutions cannot therefore accept >> legal responsibility for the contents of this message nor for any damage >> caused by viruses. This email has been scanned at the originating end. For >> further information on IT Solutions visit https://www.itsolutions.ie >> >> >> IT Solutions Email Disclaimer - The information contained in this email >> message, including any files transmitted with it, is confidential and may >> be legally privileged. >> >> This e-mail is intended only for the personal attention of the stated >> addressee(s). Any access to this email, including any files transmitted >> with it, by any other person is unauthorised. If you are not an addressee, >> you must not disclose, copy, circulate or in any other way use or rely on >> the accuracy or completeness of the information contained in this email or >> any files transmitted with it. >> >> If you have received this email in error, please inform the sender >> immediately and delete it and all copies from your system. You may not >> forward this email without the permission of the authorised sender. >> >> The views expressed in this email are those of the author, and do not >> necessarily represent the views of IT Solutions or its affiliates. Internet >> communications are not secure and IT Solutions cannot therefore accept >> legal responsibility for the contents of this message nor for any damage >> caused by viruses. This email has been scanned at the originating end. For >> further information on IT Solutions visit https://www.itsolutions.ie >> > > You **do not** need that jdbc-base jar file. You only need the files > documented: > > * The extension .jar for your database > * The JDBC driver for your database > * The schema files for your database (included in the .tar.gz file > provided for the extension in the download section of the release), which > need to be applied as documented. > > If you can provide the full logs from Guacamole (from the point that > Tomcat begins starting up), that may provide more context. Enabling > debug-level logging would also help. > > - Mike >
