LDAP Authentification failes - user object has no set display name attribute

LDAP Authentification failes - Messagelog: user object has no set display name attribute

Hi trying to connect LDAP to NC. Always get message:

[user_ldap] Warning: LDAP Login: Could not get user object for DN uid=mmustermann, ou=people,dc=DOMAIN,dc=de. Maybe the LDAP entry has no set display name attribute?

Due to LDAP Search, everything seems to be fine, but we have idea, that " displayName" has to be supplied not by “cn” as in our case. Can you confirm this or do you know workaround.

DOMAIN and UID were changed due to privacy
user@server:~$ ldapsearch -x -b “ou=People, dc=DOMAIN,dc=de” -H ldaps://ldapproxy.DOMAIN.de -D “cn=admin-nextcloud,ou=AuthConsumer,dc=DOMAIN,dc=de” -W “uid=mmustermann”
Enter LDAP Password:

extended LDIF


base <ou=People, dc=DOMAIN,dc=de> with scope subtree

filter: uid=mmustermann

requesting: ALL

mmustermann, People, DOMAIN.de

dn: uid=mmustermann,ou=People,dc=DOMAIN,dc=de
objectClass: inetOrgPerson
objectClass: organizationalPerson
objectClass: person
objectClass: top
objectClass: posixAccount
objectClass: schacPersonalCharacteristics
uid: mmustermann
cn: Max Mustermann
mail: mmustermann@DOMAIN.de

search result

search: 2
result: 0 Success

numResponses: 2

numEntries: 1

LDAP /AD Integration APP:


Adcanced settings:
Field Showname User: cn

Base-Usertree: ou=People,dc=DOMAIN,dc=de

Field Showname Group: cn

Base-Grouptree: ou=People,dc=DOMAIN,dc=de

Oblectclass: person
LDAP Filter: (|(objectclass=person))

LDAP-/AD-Benutzername: check
LDAP-/AD-E-Mail-Adresse: check
LDAP-Filter: (&(|(objectclass=person))(|(uid=%uid)(|(mailPrimaryAddress=%uid)(mail=%uid))))

Oblectclass: person
LDAP-Filter: (&(|(objectclass=person)))

Nextcloud version ( 18.0.4):
Operating system and version (Ubuntu 18.04):
Apache (Apache 2.4.29):
PHP version ( 7.2):

Can anyone help?
Thanks in Advance!

Hello, i have the same issue?
my ldap server is an HCL Domino Server.
i hope there is an workaround or an fix avilable.
Thanks thomas

Same issue here with Domino LDAP. Have you find a solution yet?