Full_Name: Carsten Klein
OS: Kubuntu 11.01
Submission from: (NULL) (126.96.36.199)
I tried to get rid of the global namespace restrictions regarding attributeType
names by declaring objectIdentifierS for each of the attributeTypeS forefront
and then use these both for declaring the attributeTypeS and also using them for
reference in a MAY or MUST clause in the declared objectClassES
While the attributeType declaration works just fine, the objectClassES will not
be parsed, resulting in an error stating that the OID cannot be resolved.
How to reproduce:
objectIdentifier fooOID 188.8.131.52.4.1.123456789
objectIdentifier fooAttrOID fooOID:1
objectIdentifier fooClassOID fooOID:2
attributeType ( fooAttrOID NAME 'fooAttr'
SYNTAX 184.108.40.206.4.1.14220.127.116.11.15 )
objectClass ( fooClassOID NAME 'fooClass' SUP top STRUCTURAL
MAY ( fooAttrOID ) )
will not work as expected.
However, replacing fooAttrOID in the above objectClass declaration by either
fooAttr or 18.104.22.168.4.1.38570.1 will produce a valid ldif when run through
I believe that the expected behaviour should be that the declared
objectIdentifier fooAttrOID should also be recognized when parsing the MAY or
MUST clause of the objectClass declaration.
Or is there a way to force slaptest to recognize it?
This is not supported. It is normal practice to use the canonical names of
attributes in objectclass definitions, for readability.
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/