I fixed this. I just needed to update my guacamole-auth-ldap-1.0.0.jar file.
Jared ________________________________ From: Nick Couchman <[email protected]> Sent: Thursday, June 7, 2018 5:19:06 AM To: [email protected] Subject: Re: Allowing LDAP attributes to be used as tokens: Internal Server Error On Wed, Jun 6, 2018 at 5:02 PM, Frees, Jared <[email protected]> wrote: > Hello, > > > This is my first post on this mailing list so please correct me if I am > doing anything the wrong way. > > > I am trying to update the guacamole code to allow arbitrary LDAP > attributes to be used as tokens. This is described in detail in JIRA issue: > GUACAMOLE-524. I have updated AuthenticationProviderService.java, > Credentials.java, StandardTokens.java, ConfigurationService.java, and > LDAPGuacamoleProperties.java to add an arbitrary number of LDAP attributes > into the Credentials object for a user and then to map those attributes as > tokens in AuthenticationProviderService.java. These attributes get > specified in guacamole.properties. > > > My code compiles fine with Maven, and I can update the WAR file in my > Tomcat server and load the new webpage, but > > when I try to login on the Guacamole login page, it returns an internal > server error and I get this error in the logs: > > Jun 06, 2018 4:07:31 PM com.sun.jersey.spi.container.ContainerResponse > logException > SEVERE: Mapped exception to response: 500 (Internal Server Error) > org.apache.guacamole.rest.APIException > A couple of questions, here: - Are there any other messages around this one that shed any light? Any other errors/warnings/etc.? You might want to configure Guacamole Client in DEBUG or TRACE mode - instructions on how to do that are here: http://guacamole.apache.org/doc/gug/configuring-guacamole.html#webapp-logging - You might want to update your fork of the git repo and rebase your changes on the current upstream master. There were some recent changes (GUACAMOLE-566) that tweak how errors are handled within the REST API, and it might actually help illuminate the issue in this case instead of throwing this relatively generic error. -Nick
