Point out that if another authorization method is used

with mod_authnz_ldap, AuthzLDAPAuthoritative must be
set to off.

submitted by: Darren Spruell <phatbuckett gmail.com>

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@499241 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/mod/mod_authnz_ldap.xml b/docs/manual/mod/mod_authnz_ldap.xml
index 9a77edd1e749b7c27b8df2eb471e37de4544529e..edab82e27b9c41d8325dfce0a9c15cb7b6217187 100644 (file)
--- a/docs/manual/mod/mod_authnz_ldap.xml
+++ b/docs/manual/mod/mod_authnz_ldap.xml
@@ -226,8 +226,14 @@ for HTTP Basic authentication.</description>
       <li>otherwise, deny or decline access</li>
     </ul>
 
-    <p>Other <directive module="core">Require</directive> values may also be 
-    used which may require loading additional authorization modules.</p>
+    <p>Other <directive module="core">Require</directive> values may also
+    be used which may require loading additional authorization modules.
+    Note that if you use a <directive module="core">Require</directive>
+    value from another authorization module, you will need to ensure that
+    <directive module="mod_authnz_ldap">AuthzLDAPAuthoritative</directive>
+    is set to <code>off</code> to allow the authorization phase to fall
+    back to the module providing the alternate
+    <directive module="core">Require</directive> value.</p>
 
     <ul>
         <li>Grant access if there is a <a href="#requser"><code>require