| Description | According to the 2.2.3 documentation, I should be able to use a URL in the form "ldaps://fully.qualified.domain.name" in the 'hostname' field of SOGoUserSources, and I can, however SOGo proceeds to talk on the wrong port number (389) instead of 686. If I force the port using the deprecated 'port' field, it connects on the correct port but still can't authenticate. The LDAP server is fine as I can authenticate using LDAPS and the same bind DN & password using another method (Apache Directory Studio.) And I can authenticate fine with no encryption. |
|---|
| Steps To Reproduce | 1) Configure sogo.conf with:
SOGoUserSources = (
{
type = ldap;
...
bindDN = "CN=SOGo,CN=Users,DC=ad,DC=example,DC=com";
bindPassword = "secret";
canAuthenticate = YES;
hostname = "ldaps://server.sub.example.com";
}
);
2) Restart SOGo and attempt to log in with valid or even invalid credentials
3) Notice the 'Could not bind to the LDAP server' message in SOGo's log file |
|---|
| Additional Information | Apr 22 19:12:31 sogod [11831]: [ERROR] <0x0x7f1eef03cf30[LDAPSource]> Could not bind to the LDAP server ldaps://server.sub.example.com (389) using the bind DN: CN=SOGo,CN=Users,DC=ad,DC=example,DC=com
Apr 22 19:12:31 sogod [11831]: [ERROR] <0x0x7f1eef03cf30[LDAPSource]> <NSException: 0x7f1eef477c40> NAME:LDAPException REASON:operation bind failed: Can't contact LDAP server (0xFFFFFFFF) INFO:{login = "CN=SOGo,CN=Users,DC=ad,DC=example,DC=com"; }
Apr 22 19:12:31 sogod [11831]: SOGoRootPage Login from '108.40.145.234' for user 'testuser' might not have worked - password policy: 65535 grace: -1 expire: -1 bound: 0
108.40.145.234 - - [22/Apr/2014:19:12:31 GMT] "POST /synapse/connect HTTP/1.1" 403 34/56 0.203 - - 3M |
|---|
