[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: ditcontentrule not allowing OID macros (ITS#2920)



At 06:49 PM 1/14/2004, Howard Chu wrote:
>> -----Original Message-----
>> From: owner-openldap-bugs@OpenLDAP.org
>> [mailto:owner-openldap-bugs@OpenLDAP.org]On Behalf Of tridge@samba.org
>
>> It seems that OID macros can't be used in ditcontentrule
>> specs. For example,
>> the
>> following schema is allowed:
>>
>> objectIdentifier myobj 1.3.6.1.4.1.7165.4
>> objectClass ( myobj:1 NAME 'class1' SUP top STRUCTURAL )
>> objectClass ( myobj:2 NAME 'class2' SUP top AUXILIARY )
>> dITContentRule ( 1.3.6.1.4.1.7165.4.1 NAME 'class1' AUX class2)
>>
>> but this schema is not currently allowed in the current CVS openldap:
>>
>> objectIdentifier myobj 1.3.6.1.4.1.7165.4
>> objectClass ( myobj:1 NAME 'class1' SUP top STRUCTURAL )
>> objectClass ( myobj:2 NAME 'class2' SUP top AUXILIARY )
>> dITContentRule ( myobj:1 NAME 'class1' AUX class2)
>>
>> I think that the two schemas should be equivalent (ie. OID
>> macros should work in
>> ditcontentrules)
>
>The ldap_str2* functions don't check the SCHEMA_ALLOW flags consistently. It
>might be cleaner to move oidmacro detection into libldap from slapd.
>Thoughts?

I rather keep the ldap_str2* functions simple parsers of RFC 2252
schema representations and keep oidmacro expansion in slapd.
Bringing it into the -lldap would imply that such macros are a
general feature of LDAP, which isn't so.

Kurt