web2ldap is known to work smoothly with the software/platforms mentioned
here. If a software is not listed here does not mean it is not compatible
unless it is listed in the negative list.
I'd appreciate if you use the feedback form
to contribute to these compability notes.
[LDAP servers]
[Web browsers]
[Operating systems]
[Web servers]
[PKI products]
- OpenLDAP 1.x
-
Open Source implementation of LDAPv2. Use is deprecated today.
- OpenLDAP 2.x
-
Open Source reference implementation of LDAPv3. Check it out!
- Netscape Directory Server 4.x and 6.x
-
web2ldap even supports some extra features for these.
- iPlanet 5.x, SunONE 5.x Directory Server
-
web2ldap even supports some extra features for these.
- Novell eDirectory 8.x
-
With sub-tree renaming, subordinate flag and some other neat features.
Some odds in sub schema of older versions.
- Lotus Domino LDAP R4.5x and 4.6x
-
Sometimes behaviour of this LDAP server was very weird making it
almost unusable. LDAPv2 if I remember correctly.
- Lotus Domino LDAP R5.x and R6.x (sometimes weird)
-
Most times it works quite well. Persistent connections are
dropped very fast - depends on the configuration I guess. web2ldap
contains a work-around for the null-byte terminated string
of the namingContexts attribute in Domino/LDAP's RootDSE.
- MS Active Directory
-
web2ldap displays the GUID as active LDAP URL links.
Various work-arounds were added to handle the broken
sub schema:
-
Handling of non-LDAPv3-compliant LDAP syntaxes in
Windows 2000 AD (Windows 2003 AD does it right).
-
Attribute objectClass explicitly added
to required attribute set when building entry data
input forms.
-
Direct links to schema object entries from sub schema
viewer.
- Siemens DirX
-
Works just fine.
- Innosoft Distributed Directory Server (IDDS)
-
At the moment only read-only tests were done.
- Critical Path InJoin 4.0
-
It's a snap. With sub-tree renaming, subordinate flag, etc.
- Syntegra
-
Read-only tests on a public address book server worked.
Not sure which type and version though.
- IBM Directory Server 5.1
-
Simply works. With subordinate flags, etc.
- Netscape Communicator 4.x
-
Chokes on rendering some CSS rules. CSS files shipped with
web2ldap distribution uses some tricks found in
hide CSS from browsers.
-
Mozilla
-
Mozilla 1.x has very good CSS support.
-
Konqueror
-
The web browser and file manager of the KDE project:
Note the input forms enclosed in <fieldset> were not displayed
by older versions.
(see KDE bug #44643 RESOLVED).
-
DILLO!
-
Very fast HTML rendering and very small! Unfortunately
currently no support for UTF-8 Unicode encoding.
- Microsoft Internet Explorer
-
Support for CSS depends very much on the version used.
-
Opera
-
Commercial browser. Aims to be fast and small.
Also very good CSS support.
- Amaya
-
W3C's reference browser.
-
lynx
-
A text-mode browser.
-
w3m
-
Another text-mode browser capable of handling tables and
displaying images (if the terminal allows it).
-
StarOffice
-
Built-in browser of the StarOffice application suite.
- Linux
-
Please do not use outdated RPM packages...
- Windows 32
-
Sucessfully tested with
Mauro's new python-ldap build.
- FreeBSD
-
- Solaris 2.8 and 2.9
-
You can grab some of the packages needed from
www.sunfreeware.com.
- Apache HTTP Server
-
I don't have to write any explanation about this one...
- lighttpd
-
You have to spawn the web2ldap FastCGI process in a separate
startup script with spawn-fcgi.
- Entrust Authority
-
Works fine with directory structure and content written by
Entrust Authority6.0 (tested with Siemens Dir/X and CP InJoin).
Displays encryption certificate in attribute userCertificate
just fine. The Entrust specific attributes (e.g. roaming profiles) can be
downloaded as binary data.
- RSA Keon CA
-
This product ships with a pretty ancient LDAPv2 server. Last time
I checked it worked to display userCertificate attribute
which is stored in old
{ASN.1}
style.
Unfortunately web2ldap cannot work with the following
misbehaving software:
-
Many Netmeeting directory servers (most times DNS alias
starting with ILS) contain invalid NUL-terminated strings in some
rootDSE attributes. This can't be worked around easily without
breaking LDAP implementation.
I also did not find a ILS server which allows non-exact searching
or any other useful stuff for general LDAP use.