Univention Bugzilla – Bug 47844
Encourage to use univentionObjectType on all LDAP objects
Last modified: 2019-03-16 19:26:08 CET
We should add a diagnostic plugin that scans through all LDAP objects and identifies those that lack "univentionObjectType" but seem to be some sort of "univention object". Also we should provide a one-click solution to add these object types.
This is important for some services to use convenient LDAP filters. Currently, the LDAP filter for users/user looks obscure and may even change at some point. Added in univention-management-console-module-diagnostic 4.0.1-1A~4.3.0.201809201635 objects beneath cn=temporary,cn=univention,$ldap_base are ignored. Also check performance issues with this new plugin. I had none.
Changelog & Advisories: OK Tested mainly with users, but also other univention objects like computer, portals etc. The module worked fine and migrated the objects. The performance was tested with 8000 users, containing 700|2000 malformed users.
As Juern figured out 81_diagnostic_checks fails: http://jenkins.knut.univention.de:8080/job/UCS-4.3/job/UCS-4.3-2/job/AutotestJoin/lastCompletedBuild/SambaVersion=no-samba,Systemrolle=master/testReport/00_checks/81_diagnostic_checks/test/
Fixed by filtering kerberos/kdcentry for now. Should be reverted as soon as Bug#47846 is fixed.
(In reply to Dirk Wiesenthal from comment #4) > Fixed by filtering kerberos/kdcentry for now. Should be reverted as soon as > Bug#47846 is fixed. OK: objects of type kerberos/kdcentry are ignored OK: YAML (5f8be4c3b9 typo) OK: Test -> verified
<http://errata.software-univention.de/ucs/4.3/352.html>
*** Bug 47366 has been marked as a duplicate of this bug. ***