This demo runs as a multi-threaded stand-alone web server.
The demon is not automatically started by my ISP,
it might be down if the machine was rebooted. Please
drop me a note in this case.
Feel free to try it with different browsers, CSS turned on and off.
You're welcome to test your own LDAP hosts with this online-demo of web2ldap
if they are accessible via Internet.
Just type in the hostname in the input field on the Connect screen.
web2ldap will try to determine the base DN/search root afterwards.
Notes about using the on-line demo:
Please report any problems or errors!
This demo reflects current development snapshot not the releases.
It might be temporarily buggy.
Do not enter confidential data!
Consider installing your own web2ldap service if you
want to maintain your LDAP server. ;-)
If anything goes wrong the exceptions are internally written
to a debug log file. I promise not to reveal any information
found therein. However you might see accesses to your LDAP
host by me while trying to fix the problem.
The demo server on this system runs with very limited
ressources (only 24 file-handles available). Therefore
the session timeouts are set to very short periods. Sometimes
you might get no response or a message "host not found"
because web2ldap cannot acquire file-handles for sockets.
Try again later in this case after unused LDAP connections have
been cleaned up. If you want to be really nice use the
The LDAP server has to be reachable via Internet and open
to the public. Especially IP addresses like 10.*, 192.168.* or
127.0.0.1 won't work. (I did not expect having to mention
this explicitly but real life shows...)
LDAP servers might behave very different because of different
LDAP protocol versions, vendor implementations and configuration.
E.g. some of the demo servers listed below are browsable
some are not, etc.
Entering the search root is optional. In most cases
browsing down the directory will automatically bring up the
search roots of the backends of a LDAP host.
However some LDAP servers are configured
to return a referral if asked for empty DN.
In this case entering the search root or any DN of
an entry on this server helps.
For security reasons the web session ID is cross-checked against
some environment variables which are assumed constant
throughout the whole session. Cut&paste of URLs will probably
not work. Also URLs containing session IDs are not persistent.
You are welcome to refer to your own LDAP host through the on-line
demo as long as it will not cause a huge amount
of traffic. Use the ldapurl command with LDAP URLs
as persistent URL. Have a look at the URLs specific examples below.
I would also appreciate if you report success stories. Use the
feedback form to ensure that you
provide all necessary information.
This section contains links to specific entries or actions
to illustrate some features.
There's a browseable LDAP repository (Siemens Dir/X) of certificates issued by
TC Trustcenter. Sometimes even the URLs in the certificates work.
You can even point to and display single
CRL with a LDAP URL.
Every web site needs a links-to-friends section (hehe).
Some of the nice guys participating in the TF-LSD groups maintain own
LDAP servers where you can look at the personal entries
(in no particular order):
Stig (thanks for nice input about web interfaces...)
Konstantin (thanks for LDAPv3 contributions to python-ldap module)