Bug 61326

Summary: the LDAP Cache not working well with multiple ldap hosts
Product: Apache httpd-2 Reporter: Icewool <qhyh>
Component: mod_ldapAssignee: Apache HTTPD Bugs Mailing List <bugs>
Status: RESOLVED LATER    
Severity: normal Keywords: MassUpdate
Priority: P2    
Version: 2.2.34   
Target Milestone: ---   
Hardware: PC   
OS: Linux   

Description Icewool 2017-07-21 16:13:34 UTC 
I use mod_authn_core's AuthnProviderAlias to create multiple ldap hosts ; you can get more inf at website:https://httpd.apache.org/docs/current/mod/mod_authn_core.html

<AuthnProviderAlias ldap ldap-a>
AuthLDAPBindDN "username"
AuthLDAPBindPassword password
AuthLDAPURL "ldap://10.0.1.55:389/OU=User Accounts,OU=Google,DC=Google,DC=com?sAMAccountName?sub?(&(objectCategory=Person)(sAMAccountName=*))"
</AuthnProviderAlias>

<AuthnProviderAlias ldap ldap-b>
AuthLDAPBindDN "username"
AuthLDAPBindPassword password
AuthLDAPURL "ldap://10.0.1.55:389/OU=User Accounts,OU=Branches,DC=Google,DC=com?sAMAccountName?sub?(&(objectCategory=Person)(sAMAccountName=*))"
</AuthnProviderAlias>

And then set the svn location：
<Location /test>
Dav svn
AuthType Basic
AuthBasicProvider ldap-a ldap-b file
AuthUserFile /data/passwd/httpwd
SVNPath /data/svnroot/test
AuthName "SVN-test"
AuthzSVNAccessFile /data/svnroot/test/conf/authz
require valid-user
SSLRequireSSL
</Location>

But I found the ldap cache only work on ldap-a; the user in ldap-b, the system didn't use ldap cache;
Comment 1 William A. Rowe Jr. 2018-11-07 21:08:55 UTC 
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.