From: Randy Terbush Date: Tue, 24 Dec 1996 19:08:24 +0000 (+0000) Subject: Update docs to reflect addition of Authoritative directive. X-Git-Tag: APACHE_1_2b3~8 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=0b7d74f2282d5a48cde66e41b35cfff68bb7e172;p=apache Update docs to reflect addition of Authoritative directive. Submitted by: Dirk vanGulik git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@77319 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_auth.html b/docs/manual/mod/mod_auth.html index 4b1816a601..ea26099968 100644 --- a/docs/manual/mod/mod_auth.html +++ b/docs/manual/mod/mod_auth.html @@ -17,6 +17,7 @@ textual files.
  • AuthGroupFile
  • AuthUserFile +
  • AuthAuthoritative
    • @@ -69,6 +70,32 @@ Security: 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 +AuthGroupFile.

    +

    +

    AuthAuthoritative

     + +Syntax: AuthAuthoritative < on(default) | off >
    +Context: directory, .htaccess
    +Override: AuthConfig
    +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. +

    +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. +

    +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. +

    See also AuthName, AuthType and AuthGroupFile.

    diff --git a/docs/manual/mod/mod_auth_db.html b/docs/manual/mod/mod_auth_db.html index 5e72af6f1a..c2566c1785 100644 --- a/docs/manual/mod/mod_auth_db.html +++ b/docs/manual/mod/mod_auth_db.html @@ -18,6 +18,7 @@ available in Apache 1.1 and later.

  • AuthDBGroupFile
  • AuthDBUserFile +
  • AuthDBAuthoritative
    • @@ -103,6 +104,30 @@ part of the problem.

    See also AuthName, AuthType and AuthDBGroupFile.

    +

    +

    AuthDBAuthoritative

     + +Syntax: AuthDBAuthoritative < on(default) | off >
    +Context: directory, .htaccess
    +Override: AuthConfig
    +Status: Base
    +Module: mod_auth

    + +Setting the AuthDBAuthoritative 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. +

    +A common use for this is in conjection with one of the basic auth modules; such +as mod_auth.c. Whereas this DB module supplies the bulk of the user credential checking; a few (administrator) related accesses fall through to a lower level with a well protected .htpasswd file. +

    +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 which might have more access interfaces. + +

    +See also AuthName, +AuthType and +AuthGroupFile.

    diff --git a/docs/manual/mod/mod_auth_dbm.html b/docs/manual/mod/mod_auth_dbm.html index b124bb1b02..201df5e7d2 100644 --- a/docs/manual/mod/mod_auth_dbm.html +++ b/docs/manual/mod/mod_auth_dbm.html @@ -17,6 +17,7 @@ DBM files.

  • AuthDBMGroupFile
  • AuthDBMUserFile +
  • AuthDBMAuthoritative
    • @@ -104,6 +105,31 @@ See also AuthName, AuthType and AuthDBMGroupFile.

    +

    +

    AuthDBMAuthoritative

     + +Syntax: AuthDBMAuthoritative < on(default) | off >
    +Context: directory, .htaccess
    +Override: AuthConfig
    +Status: Base
    +Module: mod_auth

    + +Setting the AuthDBMAuthoritative 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. +

    +A common use for this is in conjection with one of the basic auth modules; such +as mod_auth.c. Whereas this DBM module supplies the bulk of the user credential checking; a few (administrator) related accesses fall through to a lower level with a well protected .htpasswd file. +

    +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 which might have more access interfaces. + +

    +See also AuthName, +AuthType and +AuthGroupFile.

    +