mod_authz_user.xml revision d5d794fc2f4cc9ca6d6da17cfa2cdcd8d244bacd
<?xml version="1.0"?>
<!--
Copyright 2002-2004 Apache Software Foundation
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<modulesynopsis metafile="mod_authz_user.xml.meta">
<name>mod_authz_user</name>
<description>User Authorization</description>
<status>Base</status>
<identifier>authz_user_module</identifier>
<compatibility>Available in Apache 2.1 and later</compatibility>
<summary>
<p>This module provides authorization capabilities so that
authenticated users can be allowed or denied access to portions
of the web site. <module>mod_authz_user</module> grants
access if the authenticated user is listed in a <code>Require user</code>
directive. Alternatively <code>require valid-user</code> can be used to
grant access to all successfully authenticated users.</p>
</summary>
<seealso><directive module="core">Require</directive></seealso>
<seealso><directive module="core">Satisfy</directive></seealso>
<directivesynopsis>
<name>AuthzUserAuthoritative</name>
<description>Sets whether authorization will be passed on to lower level
modules</description>
<syntax>AuthzUserAuthoritative On|Off</syntax>
<default>AuthzUserAuthoritative On</default>
<contextlist><context>directory</context><context>.htaccess</context>
</contextlist>
<override>AuthConfig</override>
<usage>
<p>Setting the <directive>AuthzUserAuthoritative</directive>
directive explicitly to <code>Off</code> allows for
user authorization to be passed on to lower level modules (as defined
user</strong> matching the supplied userID.</p>
<p>By default, control is not passed on and an unknown user
will result in an Authentication Required reply. Not
setting it to <code>Off</code> thus keeps the system secure and forces
an NCSA compliant behaviour.</p>
</usage>
</directivesynopsis>
</modulesynopsis>