Samba4 loading schema.ldif

[Matthieu Patou]

Hello Geza,

>>> I've seen, that your patches were merged in master, however trying to
>>> load the attached ldif (generated with patched oLschema2ldif with
>>> X-NDS_CONTAINMENT mods) still waxes the schema. Looking at the modified
>>> schema ldb it seems, that it still misses the oMObjectClass attributes.
>>> BTW I've overcome the name collision by applying the following ldif:
>>>
>>> dn: CN=DHCP-Class,CN=Schema,CN=Configuration,DC=kzsdabas,DC=hu
>>> changetype: modify
>>> replace: lDAPDisplayName
>>> lDAPDisplayName: msdHCPClass
>>>
>>> dn: CN=dhcp-Options,CN=Schema,CN=Configuration,DC=kzsdabas,DC=hu
>>> changetype: modify
>>> replace: lDAPDisplayName
>>> lDAPDisplayName: msdhcpOptions
>>>
>>> It probably makes MS DHCP Servers useless in the Domain, but I do not
>>> intend to have any MS servers anyway.
>> Does this LDIF work against a Windows server?
>>
>> If we allow this in samba, we need to make sure that there are
>> no instances of this classes and attributes in the directory,
>> otherwise we'll get corruption.
>>
>> metze
>>
>>
> Hi,
>
> Before I would propose any inclusion or recommendation I'm going to test
> it against a Windows 2008 R2 server.
>
> BTW. I'm not really sure that this rename is needed at all, because ISC
> DHCP is looking for the cn attribute, and not the lDAPDisplayName.
But that's not that simple, you can't have two attributes with the same 
ldapdisplayname, I'm really unsure that ISC is using just CN.
When it creates and fetch object from the dhcp* classes it will check 
for attributes and those attributes have the ldapdisplayname of the 
schemaAttributes.
That means that the ldapdisplayname is really important, more important 
than the CN in fact.



My patches are at:
http://gitweb.samba.org/?p=mat/samba.git;a=shortlog;h=refs/heads/misc


It's not rebased on the latest version of master, I'll try to do it soon.

-- 
Matthieu Patou
Samba Team
http://samba.org