Chip 2000 May

home *** CD-ROM | disk | FTP | other *** search

/ Chip 2000 May / Chip_2000-05_cd1.bin / zkuste / Perl / ActivePerl-5.6.0.613.msi / 䆊䌷䈹䈙䏵-䞅䞆䞀㡆䞃䄦䠥 / _de5506e5abaaf09318db66f26170fa56 < prev next >

Wrap

Text File | 2000-03-23 | 28KB | 582 lines

<HTML> <HEAD> <TITLE>Mozilla::LDAP::Conn - Object Oriented API for the LDAP SDK.</TITLE> <LINK REL="stylesheet" HREF="../../../../Active.css" TYPE="text/css"> <LINK REV="made" HREF="mailto:"> </HEAD> <BODY> <TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0 WIDTH=100%> <TR><TD CLASS=block VALIGN=MIDDLE WIDTH=100% BGCOLOR="#cccccc"> Mozilla::LDAP::Conn - Object Oriented API for the LDAP SDK. </TD></TR> </TABLE> <A NAME="__index__"></A>  <UL> <LI><A HREF="#name">NAME</A></LI><LI><A HREF="#supportedplatforms">SUPPORTED PLATFORMS</A></LI> <LI><A HREF="#synopsis">SYNOPSIS</A></LI> <LI><A HREF="#abstract">ABSTRACT</A></LI> <LI><A HREF="#description">DESCRIPTION</A></LI> <LI><A HREF="#some perldap/oo basics">SOME PERLDAP/OO BASICS</A></LI> <LI><A HREF="#creating a new object instance">CREATING A NEW OBJECT INSTANCE</A></LI> <LI><A HREF="#performing ldap searches">PERFORMING LDAP SEARCHES</A></LI> <LI><A HREF="#modifying and creating new ldap entries">MODIFYING AND CREATING NEW LDAP ENTRIES</A></LI> <UL> <LI><A HREF="#searching and updating entries">Searching and updating entries</A></LI> <LI><A HREF="#other methods">Other methods</A></LI> </UL> <LI><A HREF="#examples">EXAMPLES</A></LI> <LI><A HREF="#installation">INSTALLATION</A></LI> <LI><A HREF="#availability">AVAILABILITY</A></LI> <LI><A HREF="#credits">CREDITS</A></LI> <LI><A HREF="#bugs">BUGS</A></LI> <LI><A HREF="#see also">SEE ALSO</A></LI> </UL>  <HR> <H1><A NAME="name">NAME</A></H1> <PRE> Mozilla::LDAP::Conn - Object Oriented API for the LDAP SDK.</PRE> <HR> <H1><A NAME="supportedplatforms">SUPPORTED PLATFORMS</A></H1> <UL> <LI>Windows</LI> </UL> <HR> <H1><A NAME="synopsis">SYNOPSIS</A></H1> <PRE> use Mozilla::LDAP::Conn; use Mozilla::LDAP::Utils;</PRE> <HR> <H1><A NAME="abstract">ABSTRACT</A></H1> This package is the main API for using our Perl Object Oriented LDAP module. Even though it's certainly possible, and sometimes even necessary, to call the native LDAP C SDK functions, we strongly recommend you use these object classes. It's not required to use our Mozilla::LDAP::Utils.pm package, but it's convenient and good for portability if you use as much as you can from that package as well. This implies using the LdapConf package as well, even though you usually don't need to use it directly. You should read this document in combination with the Mozilla::LDAP::Entry document. Both modules depend on each other heavily. <HR> <H1><A NAME="description">DESCRIPTION</A></H1> First, this is not ment to be a crash course in how LDAP works, if you have no experience with LDAP, I suggest you read some of the literature that's available out there. The LDAP Deployment Book from Netscape, or the LDAP C SDK documentation are good starting points. This object class basically tracks and manages the LDAP connection, it's current status, and the current search operation (if any). Every time you call the search method of an object instance, you'll reset it's internal state. It depends heavily on the ::Entry class, which are used to retrieve, modify and update a single entry. The search and nextEntry methods returns Mozilla::LDAP::Entry objects, naturally. You also have to instantiate (and modify) a new ::Entry object when you want to add new entries to an LDAP server. Alternatively, the <A HREF="#item_add"><CODE>add()</CODE></A> method will also take a hash array as argument, to make it easy to create new LDAP entries. To assure that changes to an entry are updated properly, we strongly recommend you use the native methods of the ::Entry object class. Even though you can modify certain elements directly, it could cause changes not to be committed to the LDAP server. If there's something missing from the API, please let us know, or even fix it yourself. <HR> <H1><A NAME="some perldap/oo basics">SOME PERLDAP/OO BASICS</A></H1> An entry consist of a DN, and a hash array of pointers to attribute values. Each attribute value (except the DN) is an array, but you have to remember the hash array in the entry stores pointers to the array, not the array. So, to access the first CN value of an entry, you'd do <PRE> $cn = $entry->{cn}[0];</PRE> To set the CN attribute to a completely new array of values, you'd do <PRE> $entry->{cn} = [ "Leif Hedstrom", "The Swede" ];</PRE> As long as you remember this, and try to use native Mozilla::LDAP::Entry methods, this package will take care of most the work. Once you master this, working with LDAP in Perl is surprisingly easy. We already mentioned DN, which stands for Distinguished Name. Every entry on an LDAP server must have a DN, and it's always guaranteed to be unique within your database. Some typical DNs are <PRE> uid=leif,ou=people,o=netscape.com cn=gene-staff,ou=mailGroup,o=netscape.com dc=data,dc=netscape,dc=com</PRE> There's also a term called RDN, which stands for Relative Distinguished Name. In the above examples, <CODE>uid=leif</CODE>, <CODE>cn=gene-staff</CODE> and <CODE>dc=data</CODE> are all RDNs. One particular property for a RDN is that they must be unique within it's sub-tree. Hence, there can only be one user with <CODE>uid=leif</CODE> within the <CODE>ou=people</CODE> tree, there can never be a name conflict. <HR> <H1><A NAME="creating a new object instance">CREATING A NEW OBJECT INSTANCE</A></H1> Before you can do anything with PerLDAP, you'll need to instantiate at least one Mozilla::LDAP::Conn object, and connect it to an LDAP server. As you probably guessed already, this is done with the new method: <PRE> $conn = new Mozilla::LDAP::Conn("ldap", "389", $bind, $pswd, $cert); die "Couldn't connect to LDAP server ldap" unless $conn;</PRE> The arguments are: Host name, port number, and optionally a bind-DN, it's password, and a certificate. If there is no bind-DN, the connection will be bound as the anonymous user. If the certificate file is specified, the connection will be over SSL, and you should then probably connect to port 636. You have to check that the object was created properly, and take proper actions if you couldn't get a connection. There's one convenient alternative call method to this function. Instead of providing each individual argument, you can provide one hash array (actually, a pointer to a hash). For example: <PRE> %ld = Mozilla::LDAP::Utils::ldapArgs(); $conn = new Mozilla::LDAP::Conn(\%ld);</PRE> The components of the hash are: <PRE> $ld->{"host"} $ld->{"port"} $ld->{"base"} $ld->{"bind"} $ld->{"pswd"} $ld->{"cert"}</PRE> and (not used in the new method) <PRE> $ld->{"scope"}</PRE> Once a connection is established, the package will take care of the rest. If for some reason the connection is lost, the object should reconnect on it's own, automatically. [Note: This doesn't work now... ]. You can use the Mozilla::LDAP:Conn object for any number of operations, but since everything is currently done synchronously, you can only have one operation active at any single time. You can of course have multiple Mozilla::LDAP::Conn instanced active at the same time. <HR> <H1><A NAME="performing ldap searches">PERFORMING LDAP SEARCHES</A></H1> We assume that you are familiar with the LDAP filter syntax already, all searches performed by this object class uses these filters. You should also be familiar with LDAP URLs, and LDAP object classes. There are some of the few things you actually must know about LDAP. Perhaps the simples filter is <PRE> (uid=leif)</PRE> This matches all entries with the UID set to ``leif''. Normally that would only match one entry, but there is no guarantee for that. To find everyone with the name ``leif'', you'd instead do <PRE> (cn=*leif*)</PRE> A more complicated search involves logic operators. To find all mail groups owned by ``leif'' (or actually his DN), you could do <PRE> (&(objectclass=mailGroup)(owner=uid=leif,ou=people,o=netscape))</PRE> The owner attribute is what's called a DN attribute, so to match on it we have to specify the entire DN in the filter above. We could of course also do a sub string ``wild card'' match, but it's less efficient, and requires indexes to perform reasonably well. Ok, now we are prepared to actually do a real search on the LDAP server: <PRE> $base = "o=netscape.com"; $conn = new Mozilla::LDAP::Conn("ldap", "389", "", ""); die "No LDAP connection" unless $conn;</PRE> <PRE> $entry = $conn->search($base, "subtree", "(uid=leif)"); if (! $entry) { # handle this event, no entries found, dude! } else { while ($entry) { $entry->printLDIF(); $entry = $conn->nextEntry(); } }</PRE> This is in fact a poor mans implementation of the ldapsearch command line utility. The search method returns an Mozilla::LDAP::Entry object, which holds the first entry from the search, if any. To get the second and subsequent entries you call the entry method, until there are no more entries. The printLDIF method is a convenient function, requesting the entry to print itself on STDOUT, in LDIF format. The arguments to the search methods are the LDAP Base-DN, the scope of the search (``base'', ``one'' or ``sub''), and the actual LDAP filter. The entry return contains the DN, and all attribute values. To access a specific attribute value, you just have to use the hash array: <PRE> $cn = $entry->{cn}[0];</PRE> Since many LDAP attributes can have more than one value, value of the hash array is another array (or actually a pointer to an array). In many cases you can just assume the value is in the first slot (indexed by [0]), but for some attributes you have to support multiple values. To find out how many values a specific attribute has, you'd call the size method: <PRE> $numVals = $entry->size("objectclass");</PRE> One caveat: Many LDAP attributes are case insensitive, but the methods in the Mozilla::LDAP::Entry package are not aware of this. Hence, if you compare values with case sensitivity, you can experience weird behavior. If you know an attribute is CIS (Case Insensitive), make sure you do case insensitive string comparisons. Unfortunately some methods in this package can't do this, and by default will do case sensitive comparisons. We are working on this, and in a future release some of the methods will handle this more gracefully. As an extension (for LDAP v3.0) we could also use schema discovery for handling this even better. There is an alternative search method, to use LDAP URLs instead of a filter string. This can be used to easily parse and process URLs, which is a compact way of storing a ``link'' to some specific LDAP information. To process such a search, you use the searchURL method: <PRE> $entry->searchURL("ldap:///o=netscape.com??sub?(uid=leif");</PRE> As it turns out, the search method also supports LDAP URL searches. If the search filter looks like a proper URL, we will actually do an URL search instead. This is for backward compatibility, and for ease of use. To achieve better performance and use less memory, you can limit your search to only retrieve certain attributes. With the LDAP URLs you specify this as an optional parameter, and with the search method you add two more options, like <PRE> $entry = $conn->search($base, "sub", $filter, 0, ("mail", "cn");</PRE> The last argument specifies an array of attributes to retrieve, the fewer the attributes, the faster the search will be. The second to last argument is a boolean value indicating if we should retrieve only the attribute names (and no values). In most cases you want this to be FALSE, to retrieve both the attribute names, and all their values. To do this with the searchURL method, add a second argument, which should be 0 or 1. <HR> <H1><A NAME="modifying and creating new ldap entries">MODIFYING AND CREATING NEW LDAP ENTRIES</A></H1> Once you have an LDAP entry, either from a search, or created directly to get a new empty object, you are ready to modify it. If you are creating a new entry, the first thing to set it it's DN, like <PRE> $entry = $conn->newEntry(); $entry->setDN("uid=leif,ou=people,o=netscape.com");</PRE> alternatively you can still use the new method on the Entry class, like <PRE> $entry = new Mozilla::LDAP::Entry;</PRE> You should not do this for an existing LDAP entry, changing the RDN (or DN) for such an entry must be done with modifyRDN. To populate (or modify) some other attributes, we can do <PRE> $entry->{objectclass} = [ "top", "person", "inetOrgPerson" ]; $entry->{cn} = [ "Leif Hedstrom" ]; $entry->{mail} = [ "leif@netscape.com" ];</PRE> Once you are done modifying your LDAP entry, call the update method from the Mozilla::LDAP::Conn object instance: <PRE> $conn->update($entry);</PRE> Or, if you are creating an entirely new LDAP entry, you must call the add method: <PRE> $conn->add($entry);</PRE> If all comes to worse, and you have to remove an entry again from the LDAP server, just call the delete method, like <PRE> $conn->delete($entry->getDN());</PRE> You can't use native Perl functions like <A HREF="../../../../lib/Pod/perlfunc.html#item_push"><CODE>push()</CODE></A> and <A HREF="../../../../lib/Pod/perlfunc.html#item_splice"><CODE>splice()</CODE></A> on attribute values, since they won't update the ::Entry instance state properly. Instead use one of the methods provided by the Mozilla::LDAP::Entry object class, for instance <PRE> $entry->addValue("cn", "The Swede"); $entry->removeValue("mailAlternateAddress", "leif@mcom.com"); $entry->remove("seeAlso");</PRE> These methods return a TRUE or FALSE value, depending on the outcome of the operation. If there was no value to remove, or a value already exists, we return FALSE, otherwise TRUE. To check if an attribute has a certain value, use the hasValue method, like <PRE> if ($entry->hasValue("mail", "leif@netscape.com")) { # Do something }</PRE> There is a similar method, matchValue, which takes a regular expression to match against, instead of the entire string. For more information this and other methods in the Entry class, see below. <PRE> =head1 OBJECT CLASS METHODS</PRE> We have already described the fundamentals of this class earlier. This is a summary of all available methods which you can use. Be careful not to use any undocumented features or heaviour, since the internals in this module is likely to change. <H2><A NAME="searching and updating entries">Searching and updating entries</A></H2> <DL> <DT><A NAME="item_add">add</A> <DD> Add a new entry to the LDAP server. Make sure you use the new method for the Mozilla::LDAP::Entry object, to create a proper entry. <DT><A NAME="item_browse">browse</A> <DD> Searches for an LDAP entry, but sets some default values to begin with, such as scope=BASE, filter=(objectclass=*) and so on. Much like search except for these defaults. Requires a DN value as an argument. An optional second argument is an array of which attributes to return from the entry. Note that this does not support the ``attributesOnly'' flag. <PRE> $secondEntry = $conn->browse($entry->getDN());</PRE> <DT><A NAME="item_close">close</A> <DD> Close the LDAP connection, and clean up the object. If you don't call this directly, the destructor for the object instance will do the job for you. <DT><A NAME="item_compare">compare</A> <DD> Compares an attribute and value to a given DN without first doing a search. Requires three arguments: a DN, the attribute name, and the value of the attribute. Returns TRUE if the attribute/value compared ok. <PRE> print "not" unless $conn->compare($entry->getDN(), "cn", "Big Swede"); print "ok";</PRE> <DT><A NAME="item_delete">delete</A> <DD> This will delete the current entry, or possibly an entry as specified with the optional argument. You can use this function to delete any entry you like, by passing it an explicit DN. If you don't pass it this argument, delete defaults to delete the current entry, from the last call to search or entry. I'd recommend doing a delete with the explicit DN, like <PRE> $conn->delete($entry->getDN());</PRE> <DT><A NAME="item_modifyRDN">modifyRDN</A> <DD> This will rename the specified LDAP entry, by modifying it's RDN. For example, assuming you have a DN of <PRE> uid=leif, ou=people, dc=netscape, dc=com</PRE> and you wish to rename to <PRE> uid=fiel, ou=people, dc=netscape, dc=com</PRE> you'd do something like <PRE> $rdn = "uid=fiel"; $conn->modifyRDN($rdn, $entry->getDN());</PRE> Note that this can only be done on the RDN, you could not change say <CODE>ou=people</CODE> to be <CODE>ou=hackers</CODE> in the example above. To do that, you have to add a new entry (a copy of the old one), and then remove the old entry. The last argument is a boolean (0 or 1), which indicates if the old RDN value should be removed from the entry. The default is TRUE (``1''). <DT><A NAME="item_new">new</A> <DD> This creates and initialized a new LDAP connection and object. The required arguments are host name, port number, bind DN and the bind password. An optional argument is a certificate (public key), which causes the LDAP connection to be established over an SSL channel. Currently we do not support Client Authentication, so you still have to use the simple authentication method (i.e. with a password). A typical usage could be something like <PRE> %ld = Mozilla::LDAP::Utils::ldapArgs(); $conn = new Mozilla::LDAP::Conn(\%ld);</PRE> Also, remember that if you use SSL, the port is (usually) 636. <DT><A NAME="item_newEntry">newEntry</A> <DD> This will create an empty Mozilla::LDAP::Entry object, which is properly tied into the appropriate objectclass. Use this method instead of manually creating new Entry objects, or at least make sure that you use the ``tie'' function when creating the entry. This function takes no arguments, and returns a pointer to an ::Entry object. For instance <PRE> $entry = $conn->newEntry();</PRE> or <PRE> $entry = Mozilla::LDAP::Conn->newEntry();</PRE> <DT><A NAME="item_nextEntry">nextEntry</A> <DD> This method will return the next entry from the search result, and can therefore only be called after a succesful search has been initiated. If there are no more entries to retrieve, it returns nothing (empty string). <DT><A NAME="item_search">search</A> <DD> The search method is the main entry point into this module. It requires at least three arguments: The Base DN, the scope, and the search strings. Two more optional arguments can be given, the first specifies if only attribute names should be returned (TRUE or FALSE). The second argument is a list (array) of attributes to return. The last option is very important for performance. If you are only interested in say the ``mail'' and ``mailHost'' attributes, specifying this in the search will signficantly reduce the search time. An example of an efficient search is <PRE> @attr = ("cn", "uid", "mail"); $filter = "(uid=*)"; $entry = $conn->search($base, $scope, $filter, 0, @attr); while ($entry) { # do something $entry = $conn->nextEntry(); }</PRE> <DT><A NAME="item_searchURL">searchURL</A> <DD> This is almost identical to search, except this function takes only two arguments, an LDAP URL and an optional flag to specify if we only want the attribute names to be returned (and no values). This function isn't very useful, since the search method will actually honor properly formed LDAP URL's, and use it if appropriate. <DT><A NAME="item_simpleAuth">simpleAuth</A> <DD> This method will rebind the LDAP connection using new credentials (i.e. a new user-DN and password). To rebind ``anonymously'', just don't pass a DN and password, and it will default to binding as the unprivleged user. For example: <PRE> $user = "leif"; $password = "secret"; $conn = new Mozilla::LDAP::Conn($host, $port); # Anonymous bind die "Could't connect to LDAP server $host" unless $conn;</PRE> <PRE> $entry = $conn->search($base, $scope, "(uid=$user)", 0, (uid)); exit (-1) unless $entry;</PRE> <PRE> $ret = $conn->simpleAuth($entry->getDN(), $password); exit (-1) unless $ret;</PRE> <PRE> $ret = $conn->simpleAuth(); # Bind as anon again.</PRE> <DT><A NAME="item_update">update</A> <DD> After modifying an Ldap::Entry entry (see below), use the update method to commit changes to the LDAP server. Only attributes that has been changed will be updated, assuming you have used the appropriate methods in the Entry object. For instance, do not use push or splice to modify an entry, the update will not recognize such changes. To change the CN value for an entry, you could do <PRE> $entry->{cn} = ["Leif Hedstrom"]; $conn->update($entry);</PRE> </DL> <H2><A NAME="other methods">Other methods</A></H2> <DL> <DT><A NAME="item_getErrorCode">getErrorCode</A> <DD> Return the error code (numeric) from the last LDAP API function call. Remember that this can only be called after the successful creation of a new :Conn object instance. A typical usage could be <PRE> if (! $opt_n) { $conn->modifyRDN($rdn, $entry->getDN()); $conn->printError() if $conn->getErrorCode(); }</PRE> Which will report any error message as generated by the call to modifyRDN. Some LDAP functions return extra error information, which can be retrieved like: <PRE> $err = getErrorCode(\$matched, \$string);</PRE> $matched will then contain the portion of the matched DN (if applicable to the error code), and $string will contain any additional error string returned by the LDAP server. <DT><A NAME="item_getErrorString">getErrorString</A> <DD> Very much like getErrorCode, but return a string with a human readable error message. This can then be used to print a good error message on the console. <DT><A NAME="item_getLD">getLD</A> <DD> Return the (internal) LDAP* connection handle, which you can use (carefully) to call the native LDAP API functions. You shouldn't have to use this in most cases, unless of course our OO layer is seriously flawed. <DT><A NAME="item_getRes">getRes</A> <DD> Just like getLD, except it returns the internal LDAP return message structure. Again, use this very carefully, and be aware that this might break in future releases of PerLDAP. These two methods can be used to call some useful API functions, like <PRE> $cld = $conn->getLD(); $res = $conn->getRes(); $count = Mozilla::LDAP::API::ldap_count_entries($cld, $res);</PRE> <DT><A NAME="item_isURL">isURL</A> <DD> Returns TRUE or FALSE if the given argument is a properly formed URL. <DT><A NAME="item_printError">printError</A> <DD> Print the last error message on standard output. <DT><A NAME="item_setRebindProc">setRebindProc</A> <DD> Tell the LDAP SDK to call the provided Perl function when it has to follow referrals. The Perl function should return an array of three elements, the new Bind DN, password and authentication method. A typical usage is <PRE> sub rebindProc { return ("uid=ldapadmin", "secret", LDAP_AUTH_SIMPLE); }</PRE> <PRE> $ld->setRebindProc(\&rebindProc);</PRE> <DT><A NAME="item_setDefaultRebindProc">setDefaultRebindProc</A> <DD> This is very much like the previous function, except instead of specifying the function to use, you give it the DN, password and Auth method. Then we'll use a default rebind procedure (internal in C) to handle the rebind credentials. This was a solution for the Windows/NT problem/bugs we have with rebind procedures written in Perl. </DL> <HR> <H1><A NAME="examples">EXAMPLES</A></H1> There are plenty of examples to look at, in the examples directory. We are adding more examples every day (almost). <HR> <H1><A NAME="installation">INSTALLATION</A></H1> Installing this package is part of the Makefile supplied in the package. See the installation procedures which are part of this package. <HR> <H1><A NAME="availability">AVAILABILITY</A></H1> This package can be retrieved from a number of places, including: <PRE> <A HREF="http://www.mozilla.org/directory/">http://www.mozilla.org/directory/</A> Your local CPAN server</PRE> <HR> <H1><A NAME="credits">CREDITS</A></H1> Most of this code was developed by Leif Hedstrom, Netscape Communications Corporation. <HR> <H1><A NAME="bugs">BUGS</A></H1> None. :) <HR> <H1><A NAME="see also">SEE ALSO</A></H1> <A HREF="../../../../site/lib/Mozilla/LDAP/Entry.html">the Mozilla::LDAP::Entry manpage</A>, <A HREF="../../../../LDAP/Mozilla:Utils.html">the LDAP::Mozilla:Utils manpage</A> <A HREF="../../../../LDAP/Mozilla:API.html">the LDAP::Mozilla:API manpage</A> and of course Perl. <TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0 WIDTH=100%> <TR><TD CLASS=block VALIGN=MIDDLE WIDTH=100% BGCOLOR="#cccccc"> Mozilla::LDAP::Conn - Object Oriented API for the LDAP SDK. </TD></TR> </TABLE> </BODY> </HTML>