Required fields & views for web authentication?

I’ve created a contacts database which I’m now trying to enable for web authentication, and not getting very far!

So far I have done the following:-

Changed the DB properties to type ‘Domino Directory’

Created and populated the following views:

($Users)

($PeopleGroupsFlat)

$PeopleGroupsHier)

Created and populated the following fields on my documents:

FirstName

LastName

FullName (type: Names)

MailAddress

Type (=“Person”)

ShortName (first initial then surname)

HTTPPassword (encrypted)

Created a Directory Assistance document enabling the database for Internet Authentication/Authorisation

Yet, if I try to login with a test user of Fred Flintstone, with a short name of fflintstone, I get the following error:

03/03/2008 17:45:27.78 [0DD0:0014-0A90] WebAuth> LOOKUP in view ($Users) (user=‘fflintstone’ org=‘/MML’)

03/03/2008 17:45:27.78 [0DD0:0014-0A90] WebAuth> No unambiguous match for user=‘fflintstone’ org=‘/MML’

…even though fflintstone is definitely listed in my ($Users) view! DA is definitely working properly, as if I replace the contacts database with an older design, authentication is successful.

So what am I missing here? What are the minimum design requirements to allow a standard Notes database to be used for web client authentication?

Subject: Required fields & views for web authentication?

If anyone stumbles across this looking for the same answer, I found it here at Vince Schuurman’s blog.