Index of /ldapconf/docs

 Name                    Last modified       Size  Description

 Parent Directory        07-Oct-2001 07:48      -  
 ANNOUNCE                22-Jan-2001 06:26     2k  
 COPYING                 22-Jan-2001 05:42    18k  
 CREDITS                 22-Jan-2001 05:42     2k  
 ChangeLog               26-Oct-2000 16:13    13k  
 ROADMAP                 20-May-2000 14:38     1k  
 TODO                    22-Jan-2001 05:42     2k  
 profiles/               22-Jan-2001 07:25      -  
 ref/                    22-Jan-2001 07:25      -

LDAPconf README
---------------

Latest modification: 2001-01-18 (ldapconf-0.18)

LICENCE

GNU Public License - Read the file COPYING

STATUS

ldapconf is currently ALPHA software. It is under development, and any structure/feature/format/etc may change - maybe without notice - in future releases.
It may work well with some directories, but it may destroy others - so be careful.
It is only recomended to use it with a test server and test data - if you use it in production, and ruin the company directory data - it is not our problem.
The best approach to do something useful with it, is probably to build a new directory using ldapconf only. It includes some support for building a new directory from scratch, but you still have do to some manual configuration of slapd config to make it work properly.

REQUIREMENTS

To use ldapconf you need to have linuxconf and openldap installed on your system.
The current release is developed using openldap-2.x, linuxconf-1.23, and RedHat-7.0.
It should work ok with openldap-1.x, but if it doesn't, you may try ldapconf-0.17, which was developed with openldap-1.x.
It should also work ok with other distributions, but you may have to change some paths to binaries and config files.
To use the client tools, you only need the basic openldap package.
To use the server tools, you also need the openldap-server package.
Please note that ldapconf *requires* openldap binaries to work - it is *not* linked with the ldap c api.

INSTALL

It is highly recommended to install ldapconf from the RPM package.
It is possible to make it from source and install it directly, but then you will get problems to uninstall all the files if you later decide to uninstall it.
Description for building the RPM packages from source is described below (it's simple).

So, to install the rpm package, you type

rpm -Uvh ldapconf-<version>.i386.rpm

This will install the module library and all the help/message files into the linuxconf lib directory, and some sample profiles into /etc/ldapconf.
It will enable the module in linuxconf, so it will show up in the linuxconf menu tree in next run.
It will also install a symlink /usr/bin/ldapconf, which will provide a 'standalone' ldapconf menu if you run it.

FIRST TIME CONFIGURATION

Depending on the version and filestructure of the installed openldap package, it may be needed to do some manual tweaking to make it work.
Some binary/file paths for various distributions is provided in the linuxconf distribution directories, in theory the correct setup should be used automatically but it doesn't work in some cases. If you get the message "missing daemon ..." you may try to set the paths manually. The preset paths are stored in:

/usr/lib/linuxconf
./redhat/ (default is for 7.0)
./redhat/6/ (for 6.x and older)
./debian/
./suse/
./std/

The paths and binary names may also be configured manually inside linuxconf, in the menu control->config command & paths.

If you get error messages from ldapsearch etc when ldapconf try to run some ldap operation, it maybe use commands for the wrong openldap version.
This may be changed in the ldapconf "module setup" dialog, located from linuxconf in Control->Misc->ldapconf->Module setup.
Check the radiobutton "openldap version", it may be set for 1.x or 2.x

Finally you probably want to set the default config for the ldapclient and ldap auth client, dialogs for this is located in Config->Network->Client->LDAP...

USAGE

todo...

DOCUMENTATION

Most of the helpfiles are a bit outdated, but some useful information may be found.
Some info is available on the ldapconf homepage.
The most accurate documentation is - as usual - in the source files.

COMPILING

To compile you need to install the linuxconf-devel RPM (and maybe linuxconf-tools, not sure if it is required anymore).
Download the source package, and untar (or checkout from cvs).

Then you may do:

make
make install (without uninstall support - mainly used for quick devel testing)
make buildrpm - compile and build RPM packages.

Sometimes you also have to:

make clean
make proto
make msg

DEVEL/CONTRIB

Hack away, there is a million things to add and fix.
Patches are most welcome, also non-code contribs like sample profiles, tips, translations, documentations updates, spelling fixes, etc.
tabsize 4

CVS

ldapconf is maintained in cvs, with anonymous read access.

CVSROOT :pserver:guest@cvs.terminator.net:/vhome/cvs/root/terminator
MODULE ldapconf
BRANCHTAG OPENLDAP-2 (the current development branch)

example: cvs -d :pserver:guest@cvs.terminator.net:/vhome/cvs/root/terminator checkout -r OPENLDAP-2 ldapconf

Active developers are granted CVS write access on request.

cvs may also be browsed from web, see the cvsweb page at http://cvs.terminator.net/

BUGS

Well there are quite some bugs included, some of them are mentioned in the TODO file.

For new and interesting bugs report them to <stein@terminator.net> or to the mailinglist.

MAILINGLIST

There is currently one mailinglist for general discussions and announcements, send mail to <majordomo@terminator.net> with subscribe in the body to join it.