On Tue, Jun 4, 2019 at 11:09 AM Vieri <[email protected]> wrote:
> On Tuesday, June 4, 2019, 3:53:10 PM GMT+2, Nick Couchman < > [email protected]> wrote: > ... > I found out that the Internal Server Error was due to the fact that I had > left the ldap jar within /etc/guacamole/extensions, and tomcat/guacamole > was complaining about ldap* config parameters not found in > guacamole.properties. This doesn't seem to be a problem with guacamole > 1.0.0 though... > Can anyone please try to place the ldap module in the extensions dir so it > is loaded in the git version, and NOT define any ldap* parameters in > guacamole.properties? > If any of the properties required by the LDAP extension are absent from guacamole.properties, the extension will fail with a fatal error. This behavior is not dependent on version, and has been this way since the dawn of support for extensions in Guacamole. If you left the .jar from the git build in place and switched back to 1.0.0, the reason you're not seeing things fail is likely because Guacamole is refusing to load the newer extension. There are version compatibility sanity checks which will stop an extension written for a newer version of Guacamole from being loaded by an older version. If this is the case, there will be a message in the logs noting that refusal to load. - Mike
