after updating NC 25.0.0 (stable) to 25.0.1 (stable) All LDAP connections have stopped working.
Error: Could not get user object for DN uid=XXXXX, ou=XXXXX=DOMAIN,dc=de. Maybe the LDAP entry has not set display name attribute?
as already mentioned after updating from NC 25.0.0 to NC 25.0.1 (stable) none of our LDAP connections worked anymore. We are using 15 different LDAP Servers on our Cloud instances. I have tested the update before on our Lab instance which is NC 25.0.1 (beta) and there the error does not appear.
We also have Enterprise on a third NC instance which is NC 24.0.7 and there the error also does not appear.
We are using the same 15 LDAP Servers on all 3 instances with basically the same LDAP configuration except for the groups the users are read from.
After rolling back to NC 25.0.0 (stable) the error is gone.
Question1: How can this happen on the the stable channel but not on the beta channel?
Question 2: What could cause the problem if there have not been made any changes to any of the 15 LDAP Servers?
It is almost impossible that 15 different LDAP Servers on 15 different locations in the whole country suddenly do not have a display name attribute set to any of 10K users
Nextcloud version 25.0.1 (stable)
Operating system Ubuntu 20.04 - all updates
The issue you are facing:
LDAP Login impossible after update from 25.0.0 (stable) to 25.0.1 (stable)vbut no changes have been made to any LDAP Server / Connection / UserObject / Group
LDAP is part of Nextcloud and included in the zip archive. Download an older Version of Nextcloud as zip or tar. Extract the archive and compare the versions of user_ldap with the one on your server (appinfo).
Make a backup of your running Nextcloud instance!
After that replace apps/user_ldap with the one from the archive.
This error (“pageMode is not a valid attribute”) comes from the collectives app and is going to be addressed in an upcoming release of the app. Disabling the app as mentioned in this answer will remove the error:
This answer in the same thread has a link to a temporary workaround so that the app can be activated again without waiting for the release containing the fix:
Same with 26.0.1. I had to replace ldap_user app to v1.15 from 25.0.6 and edit appinfo to enable 26 version.
After upgrading I got:
“message”:“LDAP Login: Could not get user object for DN cn=\u043f\u043e\u043b\u044f\u043d\u0441\u043a\u0438\u0439 \u0432\u043b\u0430\u0434\u0438\u043c\u0438\u0440 \u043d\u0438\u043a\u043e\u043b\u0430\u0435\u0432\u0438\u0447,ou=XXX,dc=domain. Maybe the LDAP entry has no set display name attribute?”
But users can be found via ldap configuration utility.
1.15 works fine.