its always easier to brak a complex problem down into small parts. For AD auth with sogo I would suggest to install some ldap command line client and test if I can access ldap first.
And if this is working then in the next step configure sogo with the same auth params. > Am 25.01.2019 um 10:14 schrieb Rowland Penny ([email protected]) > <[email protected]>: > > On Thu, 24 Jan 2019 14:48:01 -0800 > "Carl Doss" ([email protected]) <[email protected]> wrote: > > >>> >>>> On 1/24/2019 1:28 PM, Matthew Valdez ([email protected]) wrote: >>>> Hello, >>>> >>>> I am trying to setup the SOGoUserSources by using Active Directory >>>> and LDAP and for some reason I cannot seem to get it to work. I am >>>> able to login if I use the type SQL, but cannot seem to get it to >>>> work with ldap. Any help would be appreciate, this is what I have >>>> for SOGoUserSources, of course modified a little to share with you >>>> all. >>>> >>>> >>>> SOGoUserSources = ( >>>> { >>>> type = ldap; >>>> CNFieldName = cn; >>>> IDFieldName = uid; >>>> UIDFieldName = uid; >>>> baseDN = "cn=Users,dc=domain,dc=local"; >>>> bindDN = >>>> "cn=sogo,cn=Users,dc=domain,dc=local"; >>>> bindPassword = password; >>>> canAuthenticate = YES; >>>> displayName = "Shared Addresses"; >>>> hostname = "ldap://dns.dc.local:389";; >>>> id = public; >>>> isAddressBook = YES; >>>> } >>>> ); >>>> > > Taking this: > > cn=Users,dc=domain,dc=local > > and this: > > ldap://dns.dc.local:389 > > into account, is the FQDN of the AD DC really > 'dns.dc.local' ? > > To put it another way, they do not match, 'dc=domain,dc=local' will > come from your dns domain 'domain.local' so the 'hostname' should be > 'ldap://<shorthostname>' or 'ldap://<shorthostname>.domain.local' > > Rowland > > > -- > [email protected] > https://inverse.ca/sogo/lists -- [email protected] https://inverse.ca/sogo/lists
