The encrypted web connection (HTTPS) requires that you have installed
CA certificates from CAcert.org in your browser.
Otherwise you will see a browser warning.
This demo runs as a multi-threaded stand-alone web server.
The link is slow since the DSL uplink is only 256 kBit/sec.
So please be patient when playing with it.
This is a running application! So just clicking on one link
won't show you much. I'd like to encourage you to actually play
Since web2ldap loads the whole sub schema sub entry from an LDAP server
(200..400 kByte) during connecting to it it might take some time until
you see the first web page. Please be patient.
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.
Further notes about using the on-line demo:
This demo sometimes reflects current development snapshot not the releases.
It might be temporarily buggy. Please report any problems!
Note that I refuse to give any warranty of any kind
that the demo is not doing any harm to your LDAP server.
Especially if you are modifying your directory be prepared
that data might be destroyed or lost!
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 LDAP server you try to access 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
LDAP URLs as query string to define a
Also have a look at the URLs of the specific examples below to get a clue.
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 and the use of LDAP URLs as
web2ldap as generic LDAP client only displays the dynamically
retrieved content of the LDAP directories. I am not responsible
for data displayed through web2ldap in any way.
Search a server without defining the LDAP host
in the LDAP URL. This works since the DNS domain uninett.no
has a SRV record in DNS.
There's a browseable LDAP repository (Siemens DirX) 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.
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):