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.
Notes about using the on-line demo:
-
This demo 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 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
[Disconnect] link.
-
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
LDAP URLs as query string to define a persistent URL.
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.
Specific examples
This section contains links to specific entries or actions
to illustrate some features.
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.
- ldap.openldap.org
-
Several examples:
-
Find
Kurt@OpenLDAP.org via sub tree search without defining the LDAP host
in the LDAP URL. This works since the DNS domain openldap.org
has a SRV record in DNS.
-
Directly jump into the
schema browser.
- www.trustcenter.de
-
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
certificate or
CRL with a LDAP URL.
- www.nldap.com
-
The
group admin feature is helpful for quickly adding/removing an entry
to/from a group.
- TF-LSD people
-
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...)
-
Diego
- master.surfnet.nl (DIRECT project)
-
You can see how
referrals are handled by clicking on one of the C= entries, e.g.
C=ES.
-
web2ldap monitor
-
New
monitor page. Still not much information though...
- SRV RR support
-
You can
locate other LDAP servers by SRV RR.
- Jochen Keutel's page
-
Jochen Keutel maintains another interesting
list of public ldap servers incl. details and comments.
- Mozilla
-