From 280b6e2b8d825e240fd4e5671eb394298ab9cf8f Mon Sep 17 00:00:00 2001 From: brian Date: Wed, 22 Jan 1997 03:51:32 +0000 Subject: [PATCH] Cleanups, looks like a placeholder was forgotten. Also, lines really shouldn't be more than 75 characters long, unless they need to be. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@77469 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/mod_auth.html | 68 +++++++++++++++++++++++++---------- 1 file changed, 50 insertions(+), 18 deletions(-) diff --git a/docs/manual/mod/mod_auth.html b/docs/manual/mod/mod_auth.html index ea26099968..ac44fd6103 100644 --- a/docs/manual/mod/mod_auth.html +++ b/docs/manual/mod/mod_auth.html @@ -56,15 +56,15 @@ See also AuthName, Status: Base
Module: mod_auth

-The AuthUserFile directive sets the name of a textual file containing the list -of users and passwords for user authentication. Filename is the -absolute path to the user file.

-Each line of the user file file contains a username followed by a colon, -followed by the crypt() encrypted password. The behavior of multiple -occurrences of the same user is undefined.

-Note that searching user groups files is inefficient; -AuthDBMUserFile should -be used instead.

+The AuthUserFile directive sets the name of a textual file containing +the list of users and passwords for user +authentication. Filename is the absolute path to the user +file.

Each line of the user file file contains a username followed +by a colon, followed by the crypt() encrypted password. The behavior +of multiple occurrences of the same user is undefined.

Note that +searching user groups files is inefficient; AuthDBMUserFile should be +used instead.

Security: make sure that the AuthUserFile is stored outside the document tree of the web-server; do not put it in the directory that @@ -82,19 +82,51 @@ See also AuthName, Status: Base
Module: mod_auth

-Setting the AuthAuthoritative directive explicitly to 'off' allows for both authentification and authorization to be passed on to lower level modules (as defined in the Configuration and modules.c file 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 Authorization Required reply. +Setting the AuthAuthoritative directive explicitly to 'off' +allows for both authentification and authorization to be passed on to +lower level modules (as defined in the Configuration and +modules.c file 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 Authorization Required reply. +

-So if a userID appears in the database of more than one module; or if a valid require directive applies to more than one module; then the first module will verify the credentials; and no access is passed on; regardless of the AuthAuthoritative setting. + +So if a userID appears in the database of more than one module; or if +a valid require directive applies to more than one module; then the +first module will verify the credentials; and no access is passed on; +regardless of the AuthAuthoritative setting. +

-A common use for this is in conjection with one of the database modules; such -as mod_auth_db.c, mod_auth_dbm.c, -mod_auth_msql.c and mod_auth_anon.c. These modules supply the bulk of the user credential checking; but a few (administrator) related accesses fall through to a lower level with a well protected AuthUserFile. + +A common use for this is in conjection with one of the database +modules; such as mod_auth_db.c, mod_auth_dbm.c, mod_auth_msql.c and mod_auth_anon.c. These modules +supply the bulk of the user credential checking; but a few +(administrator) related accesses fall through to a lower level with a +well protected AuthUserFile. +

-Default: By default; control is not passed on; and an unkown userID or rule will result in an Authorization Required reply. Not setting it thus keeps the system secure; and forces an NSCA compliant behaviour. + +Default: By default; control is not passed on; and an unkown +userID or rule will result in an Authorization Required reply. Not +setting it thus keeps the system secure; and forces an NSCA compliant +behaviour. +

-Security: 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 AuthUserFile is stored outside the -document tree of the web-server; do not put it in the directory that -it protects. Otherwise, clients will be able to download the AuthUserFile. + +Security: 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 AuthUserFile is stored outside the document tree of the +web-server; do not put it in the directory that it +protects. Otherwise, clients will be able to download the +AuthUserFile. +

See also AuthName, AuthType and -- 2.40.0