This module allows the use of HTTP Basic Authentication to
restrict access by looking up users in plain text password and
group files. Similar functionality and greater scalability is
provided by
The
Each line of the group file contains a groupname followed by a colon, followed by the member usernames separated by spaces.
Note that searching large text files is very
inefficient;
Make sure that the
The
Each line of the user file contains a username followed by
a colon, followed by the encrypted password. If the same user
ID is defined multiple times,
The utility src/support
, is used to maintain
this password file. See the man
page for more details. In short:
Create a password file Filename
with
username
as the initial ID. It will prompt for the
password:
Add or modify username2
in the password file
Filename
:
Note that searching large text files is very
inefficient;
Make sure that the
Setting the Off
allows for both authentication and
authorization to be passed on to lower level modules (as defined in the
modules.c
files) if there is no userID
or rule matching the supplied userID. If there is a
userID and/or rule specified; the usual password and access checks
will be applied and a failure will give an "Authentication Required"
reply.
So if a userID appears in the database of more than one module;
or if a valid
A common use for this is in conjunction with one of the
database modules; such as mod_auth_msql
, and
By default control is not passed on and an unknown userID or rule will result in an "Authentication Required" reply. Not setting it thus keeps the system secure and forces an NCSA compliant behaviour.
Do consider the implications of allowing a user to allow
fall-through in his .htaccess file; and verify that this is really
what you want; Generally it is easier to just secure a single
.htpasswd file, than it is to secure a database such as mSQL.
Make sure that the