Re: [Fwd] Net::LDAP patch

[Chris R. <chr...@me...>]

Graham Barr <gb...@po...> wrote:
> ----- Forwarded message from Scott Bruce <sc...@te...> -----
> 
> Date: Fri, 11 May 2001 22:14:27 -0700
> To: gb...@po...
> From: Scott Bruce <sc...@te...>
> Subject: Net::LDAP patch
> X-Mailer: Microsoft Outlook Express 6.00.2465.0000
> 
> Hi Graham,
> 
> attached is the diff output from a quick patch I had to hack into
> Net::LDAP to get the schema stuff working with openldap 2.0.7 :-).  by
> default openldap only returns attribute data for 'objectclass' and 'cn'
> if you request the subschema object, weird, so appending the other

No, that's sort of OK. The root DSE is handled a bit vaguely in the LDAP
RFCs - to access it you should really use a manageDsaIT Control (which is
not defined by any RFCs) because it is not a normal entry in the DIT. In
the absence of this standard control servers are either 'helpful' and
return all the (operational) attributes - pretending the control's been
set, effectively - or 'strict' and don't.

For normal entries, servers are not supposed to return any operational
attributes that have not explicitly been requested. Clearly this is what
the OpenLDAP server is doing with the root.

> attribute names is neccessary if you want to do anything with the
> subschema object (like use it with Net::LDAP::Schema..).

That change was included as part of the rejig of the schema code in 0.23,
except that we also retrieve the ldapSyntaxes attribute as well.

> I found a small problem with Net::LDAP::Schema too; if an objectclass is
> missing MUST or MAY tokens (?) in the schema then Net::LDAP::Schema will
> barf when trying to construct a list of attributes for that
> objectclass....

There looks to be some code in the current Net::LDAP::Schema.pm file that
deals with this situation too.

Try getting the latest version of Net::LDAP!

Cheers,

Chris