Mike Jumper commented on GUACAMOLE-981:

I noticed that the LDAP_SEARCH_BIND_DN contains a space, so "CN=Some 
User,OU=Accounts, DC=my,DC=org". Maybe that could be an issue?

It may be, yes.

If you are still having trouble, please post to the u...@guacamole.apache.org 
list to seek assistance there. The community should be able to help figure out 
what is wrong. It is very unlikely that something this fundamental is a bug, 
and more likely that what you're seeing is due to problems in your 

> 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 
> Is there anything more that can be done to debug this?

This message was sent by Atlassian Jira

Reply via email to