web2ldap is designed to be very flexible. It can be installed in
two different modes running persistent as a multi-threaded server
process under Win32 and Unix platforms:
You can start web2ldap as stand-alone web server running
on a specific address (default is fully-qualified hostname)
and port (default 1760).
You can serve some other static web content in that mode
(e.g. the .css files).
If you are running the Apache web server you might want
to consider running web2ldap as multi-threaded FastCGIServer
Extract content of archive web2ldap-*.tar.gz to e.g. /usr/local.
Regarding directory names under several Unix flavours:
Your mileage may vary.
Rename /usr/local/web2ldap-<version> to /usr/local/web2ldap.
Choose the right script web2ldap.py for your running mode and
adjust the path to the Python interpreter executable in the
first line of the web2ldap.py script
(see also python -h for usage of option -O and -OO for running with
optimized bytecode generation).
[web2ldapdir]/fcgi/web2ldap.py should reside in a directory which
has the right mod_fastcgi directives set for running
it as a static FastCGI server.
Assuming you extracted web2ldap to /usr/local/web2ldap
you can configure it as FastCGI server with the following
The URL for accessing this web2ldap FastCGI server would be
Edit configuration modules under
which contain comments about every configuration parameter.
See also the documentation
(which is probably outdated most times ;-).
Change current directory to the directory where you extracted
web2ldap and invoke python [web2ldapdir]/sbin/compile.py or
python -O [web2ldapdir]/sbin/compile.py for compiling
all Python sources.
For a quick start as stand-alone web gateway
simply invoke the script [web2ldapdir]/sbin/web2ldap.py
which outputs the start URL before detaching from console.