hi.
i think i may have a clue on this problem:
- if the user is created with the name equal to the login, there is no problem
For example, user named 'operator' has his login as 'operator'
But the user named 'Frank Andersen' has a login like 'fandersen'. This will
give the error you stated before.
I have tried changing
IDFieldName = cn;
UIDFieldName = sAMAccountName;
to
IDFieldName = sAMAccountName;
UIDFieldName = sAMAccountName;
but now even the short named users won't logon.
What shoud be the reason for this?
TIA
My ldap (AD) config is:
<key>SOGoUserSources</key>
<array>
<dict>
<key>CNFieldName</key>
<string>cn</string>
<key>IDFieldName</key>
<string>cn</string>
<key>UIDFieldName</key>
<string>sAMAccountName</string>
<key>baseDN</key>
<string>cn=Users,dc=domain,dc=local</string>
<key>bindDN</key>
<string>CN=sogo,CN=Users,DC=domain,DC=local</string>
<key>bindPassword</key>
<string>password</string>
<key>canAuthenticate</key>
<string>YES</string>
<key>displayName</key>
<string>Active Directory</string>
<key>hostname</key>
<string>192.168.0.1</string>
<key>id</key>
<string>directory</string>
<key>port</key>
<string>389</string>
<key>scope</key>
<string>SUB</string>
<key>type</key>
<string>ldap</string>
</dict>
</array>
--
[email protected]
https://inverse.ca/sogo/lists
