From cbb818222aea20b47adbcd5e4461949d7e5d5107 Mon Sep 17 00:00:00 2001 From: Andrew Bartlett Date: Tue, 20 Apr 2010 15:35:51 +1000 Subject: s4:OpenLDAP-backend Use the new rdnval module in OpenLDAP This is rather than rdn_name, which tries to do the job on the client side. We need to leave this module in the stack for Fedora DS (and of course the LDB backend). Andrew Bartlett --- source4/setup/schema-map-openldap-2.3 | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'source4/setup/schema-map-openldap-2.3') diff --git a/source4/setup/schema-map-openldap-2.3 b/source4/setup/schema-map-openldap-2.3 index 0d38652dae..09808b6742 100644 --- a/source4/setup/schema-map-openldap-2.3 +++ b/source4/setup/schema-map-openldap-2.3 @@ -15,6 +15,10 @@ uidNumber gidNumber #The memberOf plugin provides this attribute memberOf +#'name' is the RDN in AD, but 'name' means something else in +#OpenLDAP. We use rdnValue for the mapping, but this is provided by +#the rdnval overlay. +name #These conflict with OpenLDAP builtins attributeTypes:samba4AttributeTypes 2.5.21.5:1.3.6.1.4.1.7165.4.255.7 @@ -24,8 +28,6 @@ objectClasses:samba4ObjectClasses 2.5.21.6:1.3.6.1.4.1.7165.4.255.5 subSchema:samba4SubSchema 2.5.20.1:1.3.6.1.4.1.7165.4.255.4 -#'name' is the RDN in AD, but something else in OpenLDAP -name:samba4RDN #Remap these so that we don't put operational attributes in a schema MAY modifyTimeStamp:samba4ModifyTimestamp 2.5.18.2:1.3.6.1.4.1.7165.4.255.3 -- cgit