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

Re: Schema subentry format

At 09:47 AM 3/24/00 -0500, Gary Williams wrote:
>When I request the subschema subentry from Netscape and
>OpenLDAP, the objectclasses come back with _all_ attributes
>required and allowed by that class and its superiors.  When
>I request it from IBM's Secureway Directory Server, it only
>returns the attributes for that class, exclusive of the
>superiors' attributes.  Is this behavior dictated in any
>RFC, or is this another case where clients just have to
>figure it out for themselves?

Servers should publish information as configured (statically
or dynamically) without modification of listed allowed/required
attributes or listed superiors.  That is, a server configured
with:
	( 1.2 NAME 'bar' ALLOW ( 'cn' $ 'uid' ) AUXILIARY ) 
	( 1.3 NAME 'foo' ALLOW 'cn' SUP bar AUXILIARY )

should not expand foo to:
	( 1.3 NAME 'foo' ALLOW ( 'cn' $ 'uid' ) SUP bar AUXILIARY )

nor collapsed foo to:
	( 1.3 NAME 'foo' SUP bar AUXILIARY ).

--Kurt