<compatibility>Available in version 2.1 and later</compatibility>
<summary>
- <p>This module provides authentication front-ends such as
+ <p>This module allows authentication front-ends such as
<module>mod_auth_basic</module> to authenticate users through
an ldap directory.</p>
<code>ldap-filter</code>. Other authorization types may also be
used but may require that additional authorization modules be loaded.</p>
- <p>Since v2.5.0, <a href="../expr.html">expressions</a> are supported
+ <p>Since v2.4.8, <a href="../expr.html">expressions</a> are supported
within the LDAP require directives.</p>
<section id="requser"><title>Require ldap-user</title>
authorization types with <code>dbd-group</code>, <code>dbd-login</code> and
<code>dbd-logout</code>.</p>
- <p>Since v2.5.0, <a href="../expr.html">expressions</a> are supported
+ <p>Since v2.4.8, <a href="../expr.html">expressions</a> are supported
within the DBD require directives.</p>
<section id="reqgroup"><title>Require dbd-group</title>
</section>
<section id="client">
-<title>Client Login</title>
+<title>Client Login integration</title>
<p>Some administrators may wish to implement client-side session
management that works in concert with the server-side login/logout
capabilities offered by this module, for example, by setting or unsetting
-an HTTP cookie or other such token when a user logs in or out.
-To support such integration, <module>mod_authz_dbd</module> exports an
+an HTTP cookie or other such token when a user logs in or out.</p>
+<p>To support such integration, <module>mod_authz_dbd</module> exports an
optional hook that will be run whenever a user's status is updated in
the database. Other session management modules can then use the hook
to implement functions that start and end client-side sessions.</p>
</summary>
<seealso><directive module="mod_authz_core">Require</directive></seealso>
+
<section id="requiredirectives"><title>The Require Directives</title>
<p>Apache's <directive module="mod_authz_core">Require</directive>
a user is allowed to access a resource. mod_authz_dbm extends the
authorization types with <code>dbm-group</code>.</p>
- <p>Since v2.5.0, <a href="../expr.html">expressions</a> are supported
+ <p>Since v2.4.8, <a href="../expr.html">expressions</a> are supported
within the DBM require directives.</p>
<section id="reqgroup"><title>Require dbm-group</title>
</Directory>
</highlight>
</section>
+
<directivesynopsis>
<name>AuthDBMGroupFile</name>
<description>Sets the name of the database file containing the list
authorization types with <code>group</code> and <code>group-file</code>.
</p>
- <p>Since v2.5.0, <a href="../expr.html">expressions</a> are supported
+ <p>Since v2.4.8, <a href="../expr.html">expressions</a> are supported
within the groupfile require directives.</p>
<section id="reqgroup"><title>Require group</title>
access an area of the server. Access can be controlled by
hostname, IP Address, or IP Address range.</p>
- <p>Since v2.5.0, <a href="../expr.html">expressions</a> are supported
+ <p>Since v2.4.8, <a href="../expr.html">expressions</a> are supported
within the host require directives.</p>
<section id="reqip"><title>Require ip</title>
</section>
<section id="reqlocal"><title>Require local</title>
+
<p>The <code>local</code> provider allows access to the server if any
of the following conditions is true:</p>
<highlight language="config">
Require local
</highlight>
+
</section>
<section id="proxy"><title>Security Note</title>
authorization types with <code>user</code> and <code>valid-user</code>.
</p>
- <p>Since v2.5.0, <a href="../expr.html">expressions</a> are supported
+ <p>Since v2.4.8, <a href="../expr.html">expressions</a> are supported
within the user require directives.</p>
<section id="requser"><title>Require user</title>
IS_SUBREQ<br />
HTTPS<br />
REQUEST_SCHEME<br />
+ REMOTE_ADDR<br />
+ CONN_REMOTE_ADDR<br />
</td>
</tr>
</table>