We have 3 servers all configured this way (I’ve redacted sensitive information); 2 work and 1 doesn’t:
#LDAP properties ldap-hostname:ldapserver ldap-port:389 ldap-encryption-method:none ldap-dereference-aliases:never ldap-search-bind-dn:cn="Directory Manager" ldap-search-bind-password:password ldap-user-base-dn:cn=users,cn=accounts,dc=example,dc=com ldap-username-attribute:uid ldap-group-base-dn:cn=groups,cn=accounts,dc=example,dc=com Harry From: Mike Jumper <mjum...@apache.org> Sent: Wednesday, May 20, 2020 4:01 PM To: user@guacamole.apache.org Subject: Re: Issue configuring LDAP On Wed, May 20, 2020 at 12:51 PM Devine, Harry (FAA) <harry.dev...@faa.gov.invalid<mailto:harry.dev...@faa.gov.invalid>> wrote: We have a server with version 1.0.0 installed on it. We can’t seem to log in via LDAP at all. We always get the following error: May 20 15:34:59 armt server: 15:34:59.213 [http-bio-8080-exec-5] ERROR o.a.g.a.ldap.LDAPConnectionService - Unable to connect to LDAP server: Connect Error May 20 15:34:59 armt server: 15:34:59.214 [http-bio-8080-exec-5] ERROR o.a.g.a.l.AuthenticationProviderService - Unable to bind using search DN "cn="Directory Manager"" May 20 15:34:59 armt server: 15:34:59.214 [http-bio-8080-exec-5] WARN o.a.g.r.auth.AuthenticationService - Authentication attempt from [10.143.200.108, 127.0.0.1] for user "harry.devine" failed. Our LDAP configuration is identical to another machine that is still on version 0.9.13-incubating. "cn="Directory Manager"" doesn't look like a fully qualified DN. Are you sure the configuration is the same? - Mike
