httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c...@apache.org
Subject cvs commit: httpd-docs-1.3/htdocs/manual/mod mod_auth.html
Date Mon, 10 Sep 2001 17:10:22 GMT
coar        01/09/10 10:10:22

  Modified:    htdocs/manual/mod mod_auth.html
  Log:
  	Document the 'require' keywords, including the new file-owner
  	and file-group ones.
  
  Revision  Changes    Path
  1.24      +44 -2     httpd-docs-1.3/htdocs/manual/mod/mod_auth.html
  
  Index: mod_auth.html
  ===================================================================
  RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/mod/mod_auth.html,v
  retrieving revision 1.23
  retrieving revision 1.24
  diff -u -u -r1.23 -r1.24
  --- mod_auth.html	2001/07/18 20:21:56	1.23
  +++ mod_auth.html	2001/09/10 17:10:22	1.24
  @@ -43,6 +43,11 @@
   HREF="mod_auth_db.html">mod_auth_db</A>.  HTTP Digest Authentication
   is provided by <A HREF="mod_auth_digest.html">mod_auth_digest</A>.
   
  +<p>
  +<b>Note that these credential-based security mechanisms are only
  +as strong as your Web server's security.  As a rule, they are <i>not</i> as
  +strong as the operating system's own security system.</b>
  +</p>
   
   <H2>Directives</H2>
   
  @@ -52,11 +57,48 @@
   <LI><A HREF="#authauthoritative">AuthAuthoritative</A>
   </UL>
   
  -<P>See also: <A HREF="core.html#require">require</A>
  -and <A HREF="core.html#satisfy">satisfy</A>.</P>
  +<P>See also: <A HREF="core.html#require">require</A>,
  +<A HREF="core.html#satisfy">satisfy</A>, and
  +<a href="#require">mod_auth require keywords</a>.</P>
   
   <HR>
   
  +<h2><a name="require"><code>mod_auth</code> Require Keywords</a></h2>
  +<p>
  +The <code>mod_auth</code>module supports the following keywords
  +that can be given to the <a href="core.html#require">Require</a>
  +directive:
  +</p>
  +<dl compact>
  + <dt><code>user <i>username</i> [...]</code></dt>
  + <dd>The supplied username and password must be in the
  +  <a href="#authuserfile">AuthUserFile</a> database, and the username
  +  must also be one of those listed on the Require directive.</dd>
  + <dt><code>group <i>groupname</i> [...]</code></dt>
  + <dd>The supplied username and password must be in the
  +  <a href="#authuserfile">AuthUserFile</a> database, and the username
  +  must also be a member of one of the named groups
  +  in the <a href="#authgroupfile">AuthGroupFile</a> database.</dd>
  + <dt><code>valid-user</code></dt>
  + <dd>The supplied username and password must be in the
  +  <a href="#authuserfile">AuthUserFile</a> database.
  +  Any valid username from that file will be allowed.</dd>
  + <dt><code>file-owner</code></dt>
  + <dd>[Available after Apache 1.3.20]
  +  The supplied username and password must be in the
  +  <a href="#authuserfile">AuthUserFile</a> database, and the username
  +  must also match the system's name for the owner of the file being
  +  requested.</dd>
  + <dt><code>file-group</code></dt>
  + <dd>[Available after Apache 1.3.20]
  +  The supplied username and password must be in the
  +  <a href="#authuserfile">AuthUserFile</a> database, the name of the
  +  group that owns the file must be in the
  +  <a href="#authgroupfile">AuthGroupFile</a> database, and the
  +  username must be a member of that group.</dd>
  +</dl>
  +
  +<hr>
   
   <H2><A NAME="authgroupfile">AuthGroupFile</A> directive</H2>
   <!--%plaintext &lt;?INDEX {\tt AuthGroupFile} directive&gt; -->
  
  
  

Mime
View raw message