[ https://issues.apache.org/jira/browse/GUACAMOLE-981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17084667#comment-17084667 ]
Roman Bäriswyl commented on GUACAMOLE-981: ------------------------------------------ The problem was the LDAP_USER_SEARCH_FILTER which was invalid and therefore did not find the user (it was set to the dn of the base group instead of to a real filter like objectClass). I thought in that case a different error message (user/password wrong) should show instead of an internal server error :) > LDAP Internal Error > ------------------- > > Key: GUACAMOLE-981 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-981 > Project: Guacamole > Issue Type: Bug > Components: guacamole-auth-ldap > Affects Versions: 1.1.0 > Reporter: Roman Bäriswyl > Priority: Major > > I try to get LDAP authentication working. The LDAP provider is AD. I already > have a guacamole running which connects to an AD server but this new instance > does not connect. > It always reports "The ldap authentication provider has encountered an > internal error..." > I enabled the additional logging (LOGBACK_LEVEL = debug) but that does not > really help me. > I now see things like: > Transition from state <MATCHED_DB_BR_STATE> to state <ERROR > MESSAGE_BR_STATE>, tag <0x04>, action: Store error Message > and then some DECODE_LDAP MESSAGE or MESSAGE_RECEIVED with a result code > "SUCCESS". > > Is there anything more that can be done to debug this? -- This message was sent by Atlassian Jira (v8.3.4#803005)