Univention Bugzilla – Bug 41432
Easier way to create LDAP ACLs
Last modified: 2018-04-14 13:44:10 CEST
+++ This bug was initially created as a clone of Bug #40516 +++ The univention-ldap package was forked for a customer. Changes: * Configuration parameter in slapd.conf. Issue #576 & #3153 * Disabled univention-ldap-backup cronjob. Issue #2224 * Configuration parameter in ldap.conf. Issue #3074 & #2771 Goal is to create an API or merge the fork to the product. This bug handles only "* Configuration parameter in slapd.conf. Issue #3153" Asked the author for clarification.
The intention of the linked issue #3153 is to implement, reorder and test the LDAP ACLs. The bug was created because for the customer it was sufficient to implement LDAP ACLs for system accounts: 1. each component will have it's own LDAP group for accounts (i.e. "sys-dovecot" for dovecot) 2. each ACLs have to be the minimum set of LDAP attributes the component needs read access for Furthermore it was sufficient to verify functionality of system LDAP ACLs against changes the in slapd.conf. Since LDAP ACL changes are not trivial to implement it would be helpful for this kind of purpose: 1. A test/checklist that all base system ACL's work properly. 2. A meta language (e.g Lettuce Python) to describe behaviour and prove this.
*** This bug has been marked as a duplicate of bug 21631 ***
OK, closed