perl-ldap-dev

Retrieving a specific DN

[Brian S. <bri...@ed...>]

The only way I've found I can retrieve an entry if the only thing I know =
is the distinguished name is as follows:

$dn =3D 'cn=3Dlast name,ou=3Dmessaging,o=3Deds,c=3Dus';

$result =3D $ldap->search( base   =3D> $dn,
                         scope  =3D> 'base',
                         filter =3D> '(objectclass=3D*)',
                         callback =3D> \&Display,
                     );

I can substitute other attributes for 'objectclass' provided a value =
exists.

Is there any other way?  Seems like it should be easier than this, but =
perhaps this isn't really that difficult...

Regards,

Brian Safford
Consultant, Senior
Perimeter Messaging
EDS E.solutions Messaging Services

Re: Retrieving a specific DN

[Christoph N. <en...@ap...>]

Brian,

That is the "official" way to retrieve a specific DN.  What I have never
understood is why I needed to specify a filter if I'm doing a
"base" search.  I'm sure there is some good explanation for that.

- Christoph


On Tue, 22 May 2001, Brian Safford wrote:

> The only way I've found I can retrieve an entry if the only thing I know is the distinguished name is as follows:
> 
> $dn = 'cn=last name,ou=messaging,o=eds,c=us';
> 
> $result = $ldap->search( base   => $dn,
>                          scope  => 'base',
>                          filter => '(objectclass=*)',
>                          callback => \&Display,
>                      );
> 
> I can substitute other attributes for 'objectclass' provided a value exists.
> 
> Is there any other way?  Seems like it should be easier than this, but perhaps this isn't really that difficult...
> 
> Regards,
> 
> Brian Safford
> Consultant, Senior
> Perimeter Messaging
> EDS E.solutions Messaging Services
> 

Re: Retrieving a specific DN

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

Christoph Neumann <en...@ap...> wrote:
> Brian,
> 
> That is the "official" way to retrieve a specific DN.  What I have never
> understood is why I needed to specify a filter if I'm doing a
> "base" search.  I'm sure there is some good explanation for that.

Well, all searches *require* filters, so that's one (sort of) reason.
Another reason is you may need to be able to ask does an entry match some
expression eg (&(userid=cjr)(telephoneNumber=999)). You can't do that using
other operations like compare.

Life would perhaps be simpler if LDAP had a read operation like DAP, but
remember the L in LDAP stands for Lightweight :-) and unfortunately that
means the application must work a bit harder to compensate :-(

Cheers,

Chris