Re: LDAP Whois++ server now available

Mark Prior <mrp@itd.adelaide.edu.au> Wed, 28 April 1993 10:45 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa01784; 28 Apr 93 6:45 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa01780; 28 Apr 93 6:45 EDT
Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa04433; 28 Apr 93 6:45 EDT
Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id <g.01719-0@haig.cs.ucl.ac.uk>; Wed, 28 Apr 1993 09:56:52 +0100
Received: from jarrah.itd.adelaide.edu.au by bells.cs.ucl.ac.uk with Internet SMTP id <g.04583-0@bells.cs.ucl.ac.uk>; Wed, 28 Apr 1993 09:56:38 +0100
Received: by jarrah.itd.adelaide.edu.au with SMTP (5.61+IDA+MU/UA-5.26) id AA21963; Wed, 28 Apr 1993 18:24:59 +0930
Message-Id: <9304280854.AA21963@jarrah.itd.adelaide.edu.au>
To: ietf-wnils@ucdavis.edu, ids@merit.edu, osi-ds@cs.ucl.ac.uk, ldap@terminator.rs.itd.umich.edu, quipu@cs.ucl.ac.uk
Subject: Re: LDAP Whois++ server now available
In-Reply-To: Your message of "Mon, 26 Apr 1993 22:22:34 +0930." <9304261252.AA29944@jarrah.itd.adelaide.edu.au>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 28 Apr 1993 18:24:59 +0930
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Mark Prior <mrp@itd.adelaide.edu.au>

OK there is a new version (2.1.5) already, same place as before. This
fixes a problem shown up by someone at Georgia Tech when they tried
        template=person; value=smith

This should now work as expected now, although this actual query will
result in an error message "Search failed, Insufficent access" due to
search constraints on my DSA. There are 26 Smiths and it refuses to
return anything if there are more than 10 hits (to try to stop people
trawling the database).

There is also an undocumented global constraint that may interest
people using my servers - trace. This will print out (as a system
message) the LDAP query being sent to the LDAP server (and hence onto
the DSA).

Also of note is that if you only send one token the server assumes
this is a family name. If you want to search on given names you should
use the following query
        first <value>

Although unless the name is pretty unusual you will probably only get
an insufficent access error message :-).

Mark.