Hi Francis > Set IDFieldName to the same value of UIDFieldName (sAMAccountName). I tried it and it made no difference unfortunately.
> Have you double check your credentials? If your bindDN/bindPassword is > invalid, you'll see something like this in the logs : > Could not bind to the LDAP server smdc005.abc.local (389) ... > Does this hostname resolve properly? Bind credentials seems to be fine and hostname resolving also because I don't get error which you mentioned, moreover, when I click "test" button (in Webmin) next to my new data source a window pops up with the message "success" > This won't probably work with Active Directory. It was developed for the > OpenLDAP password policy overlay. OK, so I disabled this feature. Nonetheless still cannot login with AD credentials and get the same error: Jan 13 15:21:17 sogod [26193]: SOGoRootPage Login for user 'sugar' might not have worked - password policy: 65535 grace: -1 expire: -1 bound: 0 Is this possible that it's somehow related to the domain "example.com" which is fixed in the ZEG appliance? My outlook connects perfectly with SOGo using users sogo1, sogo2, sogo3. When I created a new user in local LDAP, I can login to web interface but Outlook cannot connect to "Exchange" with this new username. Maybe ZEG appliance is not possible to accept any other users than sogo1-3 ? Regards, BK > -----Original Message----- > From: Francis Lachapelle [mailto:[email protected]] > Sent: Friday, January 13, 2012 3:03 PM > To: [email protected] > Cc: [email protected] > Subject: Re: [SOGo] Active Directory LDAP user source -- [email protected] https://inverse.ca/sogo/lists
