perl-ldap-dev

How do I keep a search from hanging?

[Bryan T. <th...@rs...>]

Hi,

How do I prevent a non-responsive server from hanging my client?  I've
tried specifying  timelimit => 10 when I invoke the search method but
the call just hangs.

I am using Net::LDAP from CPAN (G/GB/GBARR/perl-ldap-0.19.tar.gz)  under
RH linux v6.1, Perl 5.005_03

Here's the debug output produced.

> Net::LDAP=HASH(0x81b3438) sending:
>
> 30 0C 02 01 01 60 07 02 01 02 04 00 80 00 __ __ 0....`........
>
> Net::LDAP=HASH(0x81b3438) received:
>
> 30 0C 02 01 01 61 07 0A 01 00 04 00 04 00 __ __ 0....a........
>
> Bind returned: code=0, error=
> Net::LDAP=HASH(0x81b3438) sending:
>
> 30 81 8E 02 01 02 63 81 88 04 0F 6F 3D 4D 6F 74 0.....c....o=Mot
> 6F 72 6F 6C 61 2C 63 3D 55 53 0A 01 02 0A 01 02 orola,c=US......
> 02 01 00 02 01 00 01 01 00 A3 2A 04 0D 72 66 63 ..........*..rfc
> 38 32 32 4D 61 69 6C 62 6F 78 04 19 42 72 79 61 822Mailbox..Brya
> 6E 5F 54 68 61 6C 65 40 65 6D 61 69 6C 2E 6D 6F n_...@em...
> 74 2E 63 6F 6D 30 3A 04 03 75 69 64 04 0A 63 6F t.com0:..uid..co
> 6D 6D 65 72 63 65 69 64 04 09 67 69 76 65 6E 4E mmerceid..givenN
> 61 6D 65 04 07 73 75 72 6E 61 6D 65 04 0D 72 66 ame..surname..rf
> 63 38 32 32 4D 61 69 6C 62 6F 78 04 04 6D 61 69 c822Mailbox..mai
> 6C __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ l
>
Thanks,
Bryan.

--
Bryan Thale
Motorola Labs, Networking and Infrastructure Research
mailto:th...@rs...

Update to 2nd.Schema.pod.diff

[Clif H. <c-h...@ti...>]

Graham,

Disregard the first 2nd.Schema.pod.diff file I sent 
you.

Use the attached 2nd.Schema.pod.diff to make the
changes.

I found an "omission" in my original write up.

-- 

Regards,

Clif Harden           INTERNET:  c-h...@ti...

Additional changes to Schema.pod

[Clif H. <c-h...@ti...>]

Graham,

I found the schema dump command was not documented.

Attached is a diff file with my changes.
This diff was taken against a Schema.pod file that
had my earlier changes applied.

Format of the diff command;
 diff -c Schema.pod.with.clifs.changes Schema.pod >! 2nd.Schema.pod.diff

Regards,

Clif Harden           INTERNET:  c-h...@ti...

Re: How to time out queries with no result?

[Mark W. <mew...@un...>]

The timeout only applies before you get a response. Most likely the server
has sent a response to your request, thus the timeout never comes into
play.

If you think there is a bug in the timeout code, send a copy of the output
of $ldap->debug(3).

Mark

On Tue, 20 Jun 2000, Thomas Fahle wrote:

> Hi,
> 
> how to time out queries that have no result?
> 
>     use Net::LDAP;
>     use Net::LDAP::Util qw(ldap_error_name ldap_error_text) ;
> 
>    $ldap_host = 'xx.xx.xx.xx';
>    $ldap = Net::LDAP->new($ldap_host)  or die $@;
> 
>    # superbroker account
> 
>    $ldap->bind(dn             =>  'cn=Administrator,
> o=SomeCompany,ou=Members',
>                             password => 'topsecret',
>     ) or die $@;
> 
>     $base= 'o=SomeCompany, ou=Members';
> 
>     $surname = 'McDonalds';
> 
>     $searchstring = "sn=$surname";
> 
>    $result =  $ldap->search(
>                                                 base => "$base",
>                                                 filter =>
> "$searchstring",
>                                                 timelimit => '10',
>                                                 );
>    $result->code && die $result->error;
> 
>    $Number_of_Entries = $result->count;
> 
>    &handle_entries unless ( $Number_of_Entries == 0);
> 
> If the surname exists everything works fine.
> 
> But the query won't time out when there is no result.
> I've tried the $SIG{ALRM} approach, too.
> 
> 
> Enviroment:
> 
> MS-LDAP
> Net::LDAP    0.19  on a Red-Hat Linux-Box
> 
> 
> Tia
> 
> Thomas
> 
> 
> 
> 
> 

How to time out queries with no result?

[Thomas F. <in...@th...>]

Hi,

how to time out queries that have no result?

    use Net::LDAP;
    use Net::LDAP::Util qw(ldap_error_name ldap_error_text) ;

   $ldap_host = 'xx.xx.xx.xx';
   $ldap = Net::LDAP->new($ldap_host)  or die $@;

   # superbroker account

   $ldap->bind(dn             =>  'cn=Administrator,
o=SomeCompany,ou=Members',
                            password => 'topsecret',
    ) or die $@;

    $base= 'o=SomeCompany, ou=Members';

    $surname = 'McDonalds';

    $searchstring = "sn=$surname";

   $result =  $ldap->search(
                                                base => "$base",
                                                filter =>
"$searchstring",
                                                timelimit => '10',
                                                );
   $result->code && die $result->error;

   $Number_of_Entries = $result->count;

   &handle_entries unless ( $Number_of_Entries == 0);

If the surname exists everything works fine.

But the query won't time out when there is no result.
I've tried the $SIG{ALRM} approach, too.


Enviroment:

MS-LDAP
Net::LDAP    0.19  on a Red-Hat Linux-Box


Tia

Thomas

Re: Diff files for Schema.pod and Examples.pod

[Graham B. <gb...@po...>]

On Tue, Jun 20, 2000 at 08:47:13AM -0500, Clif Harden wrote:
> What I was refering to on the default schema name is that LDAP.pm
> has a default schema name of "cn=schema" if it does not find a root 
> DSE, not that the LDAP/x.500 standards have a default schema.
> 
> Bad choice of words on my part.

Do you want to update your patch and resend.

Thanks,
Graham.

Re: Diff files for Schema.pod and Examples.pod

[Clif H. <cl...@di...>]

> 
> On Mon, 19 Jun 2000 13:52:31 CDT, Clif Harden wrote:
> > + After a successful bind you are ready to retrieve the schema 
> > + information.  You do this by initializing a schema object.
> > + 
> > +  $schema = $ldap->schema();
> > + 
> > +  In this case the default schema commonName (cn) is being 
> > +  used to retrieve the schema.
> 
> That description is wrong. schema() will retrieve the schema held by 
> the server using information present in the server's root DSE. See RFC 
> 2251 section 3.4
> 
> > + or
> > + 
> > +  $schema = $ldap->schema($cn);
> > + 
> > +  In this case an alternative schema commonName (cn) is being
> > +  used to retrieve the schema.
> 
> That's wrong for similar reasons. The argument is actually the DN of a 
> subentry or entry that contains the schema.
> 
> X.500 servers will for instance, have subschema stored in subentries 
> below the points which they are mastering, eg <cn=subschema-subentry,o=Y
> oyodyne,c=US>, *not* directly below the root.
> 
> > + The default LDAP schema name is cn=schema.  However this 
> > + may not always be the case, Microsoft Exchange systems are known
> > + to build a schema commonName (cn) that is based on domain and 
> > + server name.
> 
> There is no default schema name in the standards. However, Net::LDAP 
> will guess at a DN of <cn=schema> if it cannot find the 
> subschemaSubentry attribute in the root DSE.
> 
> Looks good otherwise!
> 
> Chris
> 
> 


What I was refering to on the default schema name is that LDAP.pm
has a default schema name of "cn=schema" if it does not find a root 
DSE, not that the LDAP/x.500 standards have a default schema.

Bad choice of words on my part.

Regards,

Clif Harden           INTERNET:  c-h...@ti...

Re: Getting atrs when DN is known

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

On Sun, 18 Jun 2000 20:06:35 PDT, Yann Ramin wrote:
> Hi again,
> 
> I've been looking through the examples and documentation and can'r
> figure this one out:
> 
> How do I get object attributes if I know the object dn?
> 
> I've tried doing a search with the filter being (dn=$dn), but this
> didn't lead anywhere.  It seems inefficient knowing only, say, the cn,
> and doing searches every single time for this.
> 
> Yann

You just read the entry. LDAP does not have a read operation, so it 
must be simulated with a base object search. The search filter must be 
written to always match the entry - typically a filter of 
(objectclass=*) is used which will always work because every entry must 
have an objectclass attribute.

The reason that a filter of (dn=$dn) does not work is because entries 
do not typically have an attribute called 'dn'. Hence filtering on the 
attribute is usually meaningless.

Cheers,

Chris

Re: Diff files for Schema.pod and Examples.pod

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

On Mon, 19 Jun 2000 13:52:31 CDT, Clif Harden wrote:
> + After a successful bind you are ready to retrieve the schema 
> + information.  You do this by initializing a schema object.
> + 
> +  $schema = $ldap->schema();
> + 
> +  In this case the default schema commonName (cn) is being 
> +  used to retrieve the schema.

That description is wrong. schema() will retrieve the schema held by 
the server using information present in the server's root DSE. See RFC 
2251 section 3.4

> + or
> + 
> +  $schema = $ldap->schema($cn);
> + 
> +  In this case an alternative schema commonName (cn) is being
> +  used to retrieve the schema.

That's wrong for similar reasons. The argument is actually the DN of a 
subentry or entry that contains the schema.

X.500 servers will for instance, have subschema stored in subentries 
below the points which they are mastering, eg <cn=subschema-subentry,o=Y
oyodyne,c=US>, *not* directly below the root.

> + The default LDAP schema name is cn=schema.  However this 
> + may not always be the case, Microsoft Exchange systems are known
> + to build a schema commonName (cn) that is based on domain and 
> + server name.

There is no default schema name in the standards. However, Net::LDAP 
will guess at a DN of <cn=schema> if it cannot find the 
subschemaSubentry attribute in the root DSE.

Looks good otherwise!

Chris

Re: LDAP BOF at O'Reilly Open Source Software Convention.

[Graham B. <gb...@po...>]

On Tue, Jun 20, 2000 at 06:50:46AM -0500, Clif Harden wrote:
> 
> 
> > 
> > On Mon, Jun 19, 2000 at 04:49:25PM -0500, Clif Harden wrote:
> > > 
> > > The BOF session is setup.
> > > 
> > > 
> > > 
> > > 
> > >      LDAP and Perl LDAP
> > >      6:00pm to 7:00pm in De Anza I 
> > 
> > On which day ?
> 
> TUESDAY.

Good, my BOF is wednesday so I will be there. Providing it does not
clash with my guru session which I still do not know when it is

Graham.

Re: LDAP BOF at O'Reilly Open Source Software Convention.

[Clif H. <cl...@di...>]

> 
> On Mon, Jun 19, 2000 at 04:49:25PM -0500, Clif Harden wrote:
> > 
> > The BOF session is setup.
> > 
> > 
> > 
> > 
> >      LDAP and Perl LDAP
> >      6:00pm to 7:00pm in De Anza I 
> 
> On which day ?




TUESDAY.




> 
> > 
> >      Moderator: Clif Harden 
> >      Panelists: Mark Wilcox, Graham Barr
> > 
> >      Summary: Discussion about Lightweight Directory
> >      Access Protocol (LDAP) and how Perl LDAP can be
> >      used to access LDAP directory servers. Discussion about
> >      the future direction of Perl LDAP. 
> 
> 


Regards,

Clif Harden           INTERNET:  c-h...@ti...

Caching Net::LDAP connections

[Yann R. <at...@at...>]

Hi,

Ok, you all know me by now, that loveable person who is running into all
sorts of problems :)  Now I'm asking more for advice.  How would you
suggest I cache a Net::LDAP connection in a mod_perl system?  Do you
think its a good idea?  My test script which authenticates and uses
searches is running at a cool 1.8 hits a second, whereas the DBI
connection to the PostgreSQL server is cooking up 68 (saturating the
10Mb link between the two machines - during the LDAP test 87% idle,
during the DBI test 95% idle).  I will need to spawn an additional
connection every time for authentication of users (which gets
disconnected immediatley afterwards), but that is more of a one time
affair as a session powered by the database is created.  Lookups in LDAP
are still done for group information, odd attributes, etc, where a cache
seems useful.

Yann
-- 

--------------------------------------------------------------------
Yann Ramin			at...@at...
Atrus Trivalie Productions	www.redshift.com/~yramin
Monterey High IT		www.montereyhigh.com
ICQ 				46805627
AIM				oddatrus
Marina, CA

IRM Developer                   Network Toaster Developer
SNTS Developer                  * Developer

"All cats die.  Socrates is dead.  Therefore Socrates is a cat."
	- The Logician
--------------------------------------------------------------------

Re: LDAP BOF at O'Reilly Open Source Software Convention.

[Graham B. <gb...@po...>]

On Mon, Jun 19, 2000 at 04:49:25PM -0500, Clif Harden wrote:
> 
> The BOF session is setup.
> 
> 
> 
> 
>      LDAP and Perl LDAP
>      6:00pm to 7:00pm in De Anza I 

On which day ?

> 
>      Moderator: Clif Harden 
>      Panelists: Mark Wilcox, Graham Barr
> 
>      Summary: Discussion about Lightweight Directory
>      Access Protocol (LDAP) and how Perl LDAP can be
>      used to access LDAP directory servers. Discussion about
>      the future direction of Perl LDAP. 

LDAP BOF at O'Reilly Open Source Software Convention.

[Clif H. <c-h...@ti...>]

The BOF session is setup.




     LDAP and Perl LDAP
     6:00pm to 7:00pm in De Anza I 

     Moderator: Clif Harden 
     Panelists: Mark Wilcox, Graham Barr

     Summary: Discussion about Lightweight Directory
     Access Protocol (LDAP) and how Perl LDAP can be
     used to access LDAP directory servers. Discussion about
     the future direction of Perl LDAP. 

Regards,

Clif Harden           INTERNET:  c-h...@ti...

Re: Diff files for Schema.pod and Examples.pod

[Graham B. <gb...@po...>]

Clif,

Excellent.

Thanks you

Graham

On Mon, Jun 19, 2000 at 01:52:31PM -0500, Clif Harden wrote:
> 
> Graham,
> 
> Attached are the diff files for Schema.pod and Examples.pod.
> 
> Schema.pod
> 
> I have documented the items and item methods.
> Format of diff command:  
>    diff -c Schema.pod_v0.19 Schema.pod >! Schema.pod.diff
> 
> Examples.pod
> 
> I put in a write up and code snippet on how to get and display
> schema information.
> Format of diff command;
>    diff -c Examples.pod_v0.19 Examples.pod >! Examples.pod.diff
> 
> I will probably start looking into the matchingrules parsing 
> within the next few days.
> 
> Regards,
> 
> Clif Harden           INTERNET:  c-h...@ti...

Diff files for Schema.pod and Examples.pod

[Clif H. <c-h...@ti...>]

Graham,

Attached are the diff files for Schema.pod and Examples.pod.

Schema.pod

I have documented the items and item methods.
Format of diff command:  
   diff -c Schema.pod_v0.19 Schema.pod >! Schema.pod.diff

Examples.pod

I put in a write up and code snippet on how to get and display
schema information.
Format of diff command;
   diff -c Examples.pod_v0.19 Examples.pod >! Examples.pod.diff

I will probably start looking into the matchingrules parsing 
within the next few days.

Regards,

Clif Harden           INTERNET:  c-h...@ti...

Re: about ldap->modify

[Jim H. <ha...@us...>]

Yes, the replace operation is just that:

   $ldap->modify($dn, replace => {$attr=>$value} );

  --Jim Harle
  US Naval Academy


On Mon, 19 Jun 2000, Bouarich, Reda wrote:

> Hello people,
> I'm using a ldap->modify operation to update my entry datas, but using that,
> i'm supposed to know the value of the attribute i'm modifying
> 
> (the syntax is not respected)
> e.g-> $ldap->modify
>     delete
> 	cn => 'current value'
>    add
> 	cn=> 'new value'.
> 
> It's not convenient when i'm manipulating files!
> So, is there any other way, something like a "replace operation" or anything
> else?
> Thanks a lot.
> 
> Reda Bouarich
> Compaq Computer Corp
> tel: 04-92-95-58-65
> email: Red...@co...
> 
> 
> 
> 

about ldap->modify

[Bouarich, R. <Red...@co...>]

Hello people,
I'm using a ldap->modify operation to update my entry datas, but using that,
i'm supposed to know the value of the attribute i'm modifying

(the syntax is not respected)
e.g-> $ldap->modify
    delete
	cn => 'current value'
   add
	cn=> 'new value'.

It's not convenient when i'm manipulating files!
So, is there any other way, something like a "replace operation" or anything
else?
Thanks a lot.

Reda Bouarich
Compaq Computer Corp
tel: 04-92-95-58-65
email: Red...@co...

Re: dsml.pm update

[Graham B. <gb...@po...>]

Mark, looks good, but you seem to have the Net::LDAP::DSML::Parser package mising.

What is your problem with file handles ? The open sub seems fine, or
are you refering to process() ?

Graham.

On Sat, Jun 17, 2000 at 01:26:09PM -0500, Mark Wilcox wrote:
> Hi,
> Here's another update to the Net::LDAP::DSML module. The parser is pretty
> much done except for the schema parts (admittedly that's the majority of
> the current DSML specification, but it's going to take some new stuff into
> Net::LDAP::Schema to make it work & I don't have the time currently to put
> the work in).
> 
> In any case this adjustment enables you to use Net::LDAP::DSML in a
> callback as part of search.
> 
> In any case you can now write out DSML and parse DSML entries, which is
> pretty cool (while DSML support isn't anywhere close to LDIF yet, we'll
> be ready when it does become prevelant).
> 
> Graham, I couldn't figure out how to pass in an open-file handle and get
> it to work without using IO::File. If you can show me the trick to that,
> I'll add that to the next release.
> 
> Mark

Getting atrs when DN is known

[Yann R. <at...@at...>]

Hi again,

I've been looking through the examples and documentation and can'r
figure this one out:

How do I get object attributes if I know the object dn?

I've tried doing a search with the filter being (dn=$dn), but this
didn't lead anywhere.  It seems inefficient knowing only, say, the cn,
and doing searches every single time for this.

Yann
-- 

--------------------------------------------------------------------
Yann Ramin			at...@at...
Atrus Trivalie Productions	www.redshift.com/~yramin
Monterey High IT		www.montereyhigh.com
ICQ 				46805627
AIM				oddatrus
Marina, CA

IRM Developer                   Network Toaster Developer
SNTS Developer                  * Developer

"All cats die.  Socrates is dead.  Therefore Socrates is a cat."
	- The Logician
--------------------------------------------------------------------

dsml.pm update

[Mark W. <mew...@lo...>]

Hi,
Here's another update to the Net::LDAP::DSML module. The parser is pretty
much done except for the schema parts (admittedly that's the majority of
the current DSML specification, but it's going to take some new stuff into
Net::LDAP::Schema to make it work & I don't have the time currently to put
the work in).

In any case this adjustment enables you to use Net::LDAP::DSML in a
callback as part of search.

In any case you can now write out DSML and parse DSML entries, which is
pretty cool (while DSML support isn't anywhere close to LDIF yet, we'll
be ready when it does become prevelant).

Graham, I couldn't figure out how to pass in an open-file handle and get
it to work without using IO::File. If you can show me the trick to that,
I'll add that to the next release.

Mark

Re: [Fwd] Net::LDAP::Entry

[Mark W. <mew...@un...>]

Two distinct entries cannot have the same DN. DNs MUST be unique. 

Mark

On Fri, 16 Jun 2000, Graham Barr wrote:

> ----- Forwarded message from Kimmo Hovi <kim...@ev...> -----
> 
> Date: Fri, 16 Jun 2000 14:15:29 +0200 (EET)
> From: Kimmo Hovi <kim...@ev...>
> To: gb...@po...
> Subject: Net::LDAP::Entry
> 
> Umm, this one problem I haven't quite grasped...
> 
> I hope you can answer this since I found _no_ documentation on it
> elsewhere...
> 
> I have this directory, with a single "root" class.
> objects of this rootclass can have several "leaf"classes...
> How do I access their data, their dn is the same as the root classes...
> 
> 
> 
> ----- End forwarded message -----
> 
> 

novel idea

[Graham B. <gb...@po...>]

Check out this page

http://www.ypass.net/php/ldap/

It is an LDAP class for PHP, but it allows you to traverse it like a normal
filesystem.

Graham.

[Fwd] Net::LDAP::Entry

[Graham B. <gb...@po...>]

----- Forwarded message from Kimmo Hovi <kim...@ev...> -----

Date: Fri, 16 Jun 2000 14:15:29 +0200 (EET)
From: Kimmo Hovi <kim...@ev...>
To: gb...@po...
Subject: Net::LDAP::Entry

Umm, this one problem I haven't quite grasped...

I hope you can answer this since I found _no_ documentation on it
elsewhere...

I have this directory, with a single "root" class.
objects of this rootclass can have several "leaf"classes...
How do I access their data, their dn is the same as the root classes...



----- End forwarded message -----

change to Schema.pm

[Graham B. <gb...@po...>]

I have just uploaded to CVS the following change. It's mainly performance
tweaks, but it does also allow a ::Entry object to be passed directly.

Also, The API should now really be

  $schema = Net::LDAP::Schema->new;
  $schema->parse( $entry ) or die $schema->error;

But of course the previous API of ->new( $entry ) still works as it
did, you just cannot access the error string.

Graham.