Full_Name: Ali POUYA Version: 2.4.24 OS: Redhat EL5 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (145.242.11.3) When used in conjunction with the translucent overlay, the rwm overlay filters out auxiliary objectclasses To produce the problem in the test environment you can proceed as follows : # Go to the tests directory : cd openldap-2.4.24/tests # Save the files which will be modified : cp data/test-translucent-add.ldif data/test-translucent-add.ldif.orig cp data/slapd-translucent-local.conf data/slapd-translucent-local.conf.orig # Add an auxiliary objectClass to the local directory LDIF file : cat >> data/test-translucent-add.ldif << ! > objectClass: extensibleObject > ! # Run the translucent test : ./run test034-translucent # The test does not succed, which is normal because we added an auxiliary objectClass. # Now simply add "overlay rwm" in the local config : sed -i 's/^database config/\noverlay rwm\n\ndatabase config/' data/slapd-translucent-local.conf # The test succeeds ! meaning that the auxiliary objectClass was filtered out by the rwm (was hided). I confirm that rwm works fine for the auxiliary objectClasses when used without the translucent overlay. Thanks for your help Best Regards Ali Pouya
Hi all, Can someone help me about this problem ? We use Samba in our project and it needs some auxiliary classes which disappear in this configuration. The design of my project depends on the correction of this bug. Thanks a lot Best Regards Ali Pouya
Note, this bug is not related to auxiliary classes. The same thing happens if you add a superclass like 'top' instead of extensibleObject. ali.pouya@free.fr writes: > Can someone help me about this problem ? > We use Samba in our project and it needs some auxiliary classes which > disappear in this configuration. > The design of my project depends on the correction of this bug. OpenLDAP is volunteer-driven, currently busy with migration from CVS to Git, and we'll get to the bug when we get to it. If you can't wait to see if that'll be soon, the openldap-technical mailinglist has a wider readership than the bug database. Maybe your problem can be solved differently if you describe what you want in more detail, and someone there can think of how: http://www.openldap.org/lists/mm/listinfo/openldap-technical Or you can pay someone to fix the bug: http://www.openldap.org/support/ I can think of a things to try myself. Maybe you can rearrange your setup to put rwm on another database, or maybe it's a recent bug and it works with an earlier OpenLDAP version. -- Hallvard
moved from Incoming to Software Bugs
Is this still relevant since Samba4 uses its own ldap server?