schema definition parser doesn't follow RFC2251 syntax
Status: Alpha
Brought to you by:
akarasulu
I transplanted a schema definition from iPlanet
(conformant to the RFC2251 syntax) into ldapd, and the
schema parser barfed, telling me that the
'attributeTypes:' and 'objectClasses:' entries were
illegal, along with the 'dn: cn=schema' line.
I've had to modify all of my LDAPv3 schemas to allow
ldapd to use them...shouldn't this follow a
standardized syntax?
For reference: http://www.faqs.org/rfcs/rfc2251.html
Logged In: YES
user_id=630512
The ldapd schema parser uses the OpenLdap syntax for
schema definitions which is slightly different from the
specification in 2252 I think. Anyway the syntax is slightly
modify yes you are right.
We chose to use the OpenLdap definitions and hence their
format because we were LAZY and did not want to rewrite
their attribute and object class definitions all over again. It
would be nice to change this to the standard but the parser
definition would need to be changed.
We figured if OpenLdap keeps updating its schema definition
files we can use them without copy right issues. Let me
know if this is a serious problem in your mind and we can put
it into our goals to revamp the schema parser.
-Alex