Hi,
We have been doing that for years. Config like this:
SOGoUserSources = (
{
type = ldap;
CNFieldName = displayName;
IDFieldName = cn;
UIDFieldName = uid;
bindFields = (sAMAccountName, cn);
baseDN = "CN=Users,DC=samba,DC=company,DC=com";
canAuthenticate = YES;
listRequiresDot = NO;
bindDN = "cn=sogo_search,cn=users,dc=samba,dc=company,dc=com";
bindPassword = very_secret;
displayName = "AD Internal Users";
MailFieldNames =(mail, otherMailbox, proxyAddresses);
hostname = "ldap://127.0.0.1:389";;
id = ad-users;
isAddressBook = YES;
port = 389;
scope = "SUB";
filter = "((samAccountType=805306368) AND (mail='*') AND (NOT
userAccountControl:1.2.840.113556.1.4.803:=2))";
}
As you can see, we have sogo talk ldap to 127.0.0.1:389, which is where
haproxy is listening. HAProxy is configured to talk to our three AD
servers, doing the failover etc.
Hope this helps?
MJ
On 20-3-2018 15:56, Götz Reinicke ([email protected]) wrote:
Hi,
I try to use our samba 4 ad as the user source but looks like I miss an point
or option.
I have added a dedicated user to the ad, edited the config and restarted
SOGo&memcached.
From the logs so far I guess it’s a SSL problem.
May be someone has already a working set and can share the hints and doc how to
use that?
Thanks & Regards . Götz
--
[email protected]
https://inverse.ca/sogo/lists
