Aleksey,
Thank you for your response!
While modifying the sogo.conf per your instructions, I noticed an extra
space between dc=lan in the base DN. I corrected that, and with your
changes, it works! Well, sort of.
Now, I login and the web page welcomes me by my full name, but logs me
right
Hallo! I had same problem some times ago. Try change according fields in
your config in SOGoUserSources section:
CNFieldName = cn;
IDFieldName = cn;
UIDFieldName = sAMAccountName;
bindFields = (sAMAccountName);
id = directory;
And add in there, in
Hi Christian,
Good catch.
I forgot to mention that I editted my samba.conf to allow non SSL ldap
traffic.
I tested/verified that by connecting to my Samba server with an LDAP editor
(non-ssl) and it worked.
So, will SOGo work unencrypted?
Thanks!
Keith
On Tue, Apr 9, 2019 at 3:12 PM
Iam not 100% sure but you connect without ssl/TLS I don't know if Samba
AD permits this.
We use LDAPS and it works. You then need to configure
/etc/openldap/ldap.conf to accept your certificates.
Regards
Christian
Am 09.04.19 um 17:16 schrieb Keith Howard (kbhoward1...@gmail.com):
> Hello,
>
>
Hello,
I am using Samba 4.9.4 compiled from source, MariaDB 5.5..60-1 (RPM), and
SOGo 4.0.7 (nightly RPMs).
sogo.conf:
{
/* * Main SOGo configuration file
**
*
*
* Since the content of this file is a dictionary in OpenStep plist
format, *
* the
