Univention Bugzilla – Bug 35248
connector/ldap/binddn not corrected while initial join
Last modified: 2015-02-27 15:19:40 CET
I saw this at two systems: Due to an incorrect (and mostly unknown) procedure while creating/joining a new school slave, the ucr variable "connector/ldap/binddn" was set to a wrong dn (standard dc container and not underneath a school ou). Of course this leads to an authentification error at the s4-connector (auth with a wrong hostdn as binddn). I think we should set (strict override without ?) the variable to ldap/hostdn at school slaves if its an "initial" join/rejoin. From my point of view a "univention-join" should always restore default behaviour in such cases.
Happend at 2015012521000152 - I installed S4 at the slave before the first join - therefore the ucr variables got set and pointed to the old dn of the slave (before it gets moved to the school ou).
Fixed, changelog adjusted.
Code: OK Tests: OK Changelog: OK
UCS@school 4.0 v2 has been released: http://docs.univention.de/release-notes-ucsschool-4.0v2-de.html If this error occurs again, please use "Clone This Bug".