(See the official definitions from the manual below.)
I find these definitions confusing. For NoDefaultIfFound, it says "Radiator
will only look for a DEFAULT if there were no entries found in the user
database for the user". In that case, shouldn't this be called
DefaultIfNotFound?
The reason this came up is that our <AuthBy LDAP2> was doing the latter even
WITHOUT specifying NoDefaultIfFound: any time a username did not exist, it
looked again for DEFAULT, wasting time (since we don't use a DEFAULT user).
Is NoDefaultIfFound supposed to be on by default for LDAP2? Anyway, we
appear to have gotten around this by specifying NoDefault. But note that
this explanation is also incomplete; it says that it consults DEFAULT when
it "finds [a user], but the users check items fail". However, at least for
LDAP2, it ALSO consults DEFAULT when the user doesn't exist at all.
If I am confused, I'll be glad if someone can clear this up. But hopefully
this is a clarification that will help someone else out there. Thanks for
listening!
Dave
_______________________________
6.16.11 NoDefault
Normally if Radiator searches for a user in the database and finds one, but
the users check items fail, Radiator will then consult the DEFAULT user
entry. However, if the NoDefault parameter is set, Radiator will never look
for a DEFAULT.
# Save time by never looking for a default
NoDefault
6.16.12 NoDefaultIfFound
Normally if Radiator searches for a user in the database and finds one, but
the users check items fail, Radiator will then consult the DEFAULT user
entry. However, if the NoDefaultIfFound parameter is set, Radiator will only
look for a DEFAULT if there were no entries found in the user database for
the user.
# don't fall through to DEFAULT if a users check item failed
NoDefaultIfFound
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
