- THE LDAP-WIZARD PREFERENCES
- AUTHORS AND COPYRIGHT
- SEE ALSO
Wizard::LDAP - Administration interface for your LDAP server
# From the shell: ldapWizard # Or, from the WWW: <a href="ldap.ep">LDAP administration</a>
This is a package for administration of an LDAP server. It allows to feed users, hosts and networks into the server.
First of all, you have to install the prerequisites. There are lots of:
- An LDAP Server
You need some LDAP server. We are using the OpenLDAP server, see
In theory any other LDAP server should do, but the servers configuration might be different.
A source RPM for Red Hat Linux is available on demand.
To configure the LDAP server, edit the file topics.ldif from the distribution. Currently it looks like
dc=ispsoft, dc=de objectclass: organization o: My Organization Name dn: topic=user, dc=ispsoft, dc=de name: user objectclass: topic dn: topic=net, dc=ispsoft, dc=de name: net objectclass: topic
Change "dc=ispsoft, dc=de" and the organization name to reflect your local settings. For example, if you are using the mail domain "mycompany.com", then you might choose
Import the file into your LDAP server by using the command
ldif2ldbm -i topics.ldif
(The above command will trash an existing LDAP database! Use ldapadd if you want to avoid this.)
Append the files slapd.at.conf.APPEND and slapd.oc.conf.APPEND to your /etc/openldap/slapd.at.conf and /etc/openldap/slapd.oc.conf and restart the OpenLDAP server.
This is a Perl package for atomic operations on important files.
If you like to use the WWW administration interface, you need the embedded Perl system HTML::EP.
Another Perl module, available at the same place.
To talk to the LDAP server, we use Graham Barr's Net::LDAP package. It is written in 100% Perl, no underlying C library required.
Used to determine conformance of host IP´s to a network.
All the above packages are available on any CPAN mirror, for example
or perhaps at the same place where you found this file. :-)
Note that some of the packages have their own requirements. For example, HTML::EP depends on libwww and the MailTools. If so, you will be told while installing the modules. See below for the installation of the Perl modules.
Installing a Perl module is always the same:
gzip -cd Wizard-LDAP-0.1005.tar.gz | tar xf - cd Wizard-LDAP-0.1005 perl Makefile.PL make make test make install
Alternatively you might try using the automatic installation that the CPAN module offers you:
perl -MCPAN -e shell install Bundle::Wizard::LDAP
Note that some of the modules, in particular HTML::EP, need additional configuration tasks, for example modifying the web servers configuration files.
You have to create a directory /etc/Wizard-LDAP and make it owned by the httpd user, so that CGI binaries can write into this directory.
Copy the file ldap.ep and the file gethelp.ep from the Wizard distribution into your web servers root directory. (I choose /home/httpd/html/admin/ldap.ep on my Red Hat Linux box.)
Point your browser too the corresponding location, for example
Start with modifying the preferences. See "THE LDAP-WIZARD PREFERENCES".
The system wide preferences are accessible via the web form ldap.ep. The following items can be configured:
This is the IP address of the LDAP server being used, typically
No default is set.
Likewise, this is the LDAP servers port number. The default is
This is the distinguished name to use for accessing the LDAP server as root. No default is set. Example:
cn=root, dc=ispsoft, dc=de
This is the password to use for binding to the LDAP server as root. Currently the password *must* be stored in clear text. (This is subject to change.)
This the next numeric UID, that will assigned to a new user. By default the value
is choosen. The value is incremented with any new user, so after inserting the next users it will be 501, 502, 503 and so on. You typically should reserve some block of Unix UID's for users managed by the LDAP server.
This is the numeric GID, that your LDAP users will have under Unix. The default is
This is the prefix to use for the users home directories, for example
(the default). The users login names will be appended.
This is a suffix for constructing the distinguished names of your users. Example:
A similar suffix for constructing the distinguished names of nets. Example:
The mail domain appended to unclassified email adresses. For example, if you have a user "joe" and the domain is "ispsoft.de", then its email adress will be firstname.lastname@example.org.
If you enter a shell command here, then this command will be launched after any change of the preferences. Example:
This is a similar shell command that will be called after hosts have changed. Example:
A shell command to issue after network definitions have changed. Example:
This is a special case of the command for changing users. If defined, it will be issued after a user was created. The users name will be appended as the last argument. If not defined, the above and more generic command will be executed.
Similar to item_ldap_prefs_userchange_new, but for modified users. Again, the users name will be appended as a last argument.
Finally a shell command being executed after a user has been deleted. The users name will be appended as a last argument.
This module is
Copyright (C) 1999 Jochen Wiedmann Am Eisteich 9 72555 Metzingen Germany Email: email@example.com and Amarendran R. Subramanian Grundstr. 32 72810 Gomaringen Germany Email: firstname.lastname@example.org
All Rights Reserved.
You may distribute under the terms of either the GNU General Public License or the Artistic License, as specified in the Perl README file.
1 POD Error
The following errors were encountered while parsing the POD:
- Around line 95:
Non-ASCII character seen before =encoding in 'IP´s'. Assuming ISO8859-1