Bug 50296 - LDAPVerifyServerCert and possibly LDAPTrustedMode should be moved to Virtual Host or Directory Context
Summary: LDAPVerifyServerCert and possibly LDAPTrustedMode should be moved to Virtual ...
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_authz_ldap (show other bugs)
Version: 2.2.16
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate
Depends on:
Blocks:
 
Reported: 2010-11-18 19:25 UTC by Munroe
Modified: 2018-11-07 21:09 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Munroe 2010-11-18 19:25:38 UTC
At the moment, these two parameters are only allowed in the server config context

LDAPTrustedMode
LDAPVerifyServerCert


However, as my current use case illustrates, being forced to globally set these parameters instead of on a per LDAP server basis creates unwanted behavior.

I have two different directories that are secured using LDAPS - one uses a self-signed cert that I need to set 'LDAPVerifyServerCert off' but the other one has an authentic certificate that ignoring exposes that directory to possible security issues.

Ideally I would want to put these parameters in my <AuthnProviderAlias ldap myconnection> context, along with all of the LDAP server specifics.
Comment 1 William A. Rowe Jr. 2018-11-07 21:09:23 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.