Bug 44923 - consequences of multiple LDAPTrustedGlobalCert
Summary: consequences of multiple LDAPTrustedGlobalCert
Status: RESOLVED WORKSFORME
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Documentation (show other bugs)
Version: 2.5-HEAD
Hardware: PC Linux
: P4 minor (vote)
Target Milestone: ---
Assignee: HTTP Server Documentation List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-02 07:40 UTC by Eric Covener
Modified: 2020-01-03 20:05 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Covener 2008-05-02 07:40:35 UTC 
Multiple occurences of LDAPTrustedGlobalCert essentially make repeated calls to the LDAP SDK -- my guess is that most of them end up with the last setting we push *for the same certype* as opposed to accumulating them.

This appears to the be the case for at least openldap, any thoughts from Novell/Mozilla SDK users would be interesting -- I tentatively plan to add an openldap-specific Note.
Comment 1 Rich Bowen 2010-10-29 11:07:17 UTC 
Moving docs bugs to docs@httpd.a.o ownership.
Comment 2 Mina Galić 2010-11-04 15:19:30 UTC 
If that is true. And I believe to remember that it is, trying it myself with OpenLDAP -- but I don't know if mod_ldap wasn't compiled against an OpenLDAP that was linked against GnuTLS, which has very strange kind of restrictions.

Anyway, does that mean that: http://httpd.apache.org/docs/current/mod/mod_ldap.html#settingcerts this example is wrong too?
As you're saying, you know it's true for OpenLDAP..
Comment 3 Rich Bowen 2020-01-03 19:47:39 UTC 
Eric - or anyone - what is the status of this issue? It's been open for almost 12 years now, and it would be nice to have some resolution.
Comment 4 Eric Covener 2020-01-03 20:05:25 UTC 
Since the examples all use "different" type args and nobody else ever asked, probably safest to leave it alone.