Bug 44981 - Digital Certificates (CN Based) for Authorization with active directory
Summary: Digital Certificates (CN Based) for Authorization with active directory
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_auth_ldap (show other bugs)
Version: 2.0.49
Hardware: PC Linux
: P1 enhancement (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2008-05-12 22:49 UTC by durgesh
Modified: 2018-11-07 21:09 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description durgesh 2008-05-12 22:49:20 UTC

I am very new to apache http server and having one specific security requirement.

I need to have Client certificate based authorization enabled at apache and apache should extract the field CN from client certificate passed to apache while SSL communication and apache should look with in active directory for existance of that CN (cn for Active Directory).

- allow if client certificate's CN matches with entry with in active directory (cn).
- deny if client certificate's CN does not match with any entry from active directory (cn).

Comment 1 Peter Thomas 2010-02-22 15:28:40 UTC
I believe that the non-default option in my proposed #48780 would achieve what you are looking for when used without any Require* directives except for "valid-user."
Comment 2 William A. Rowe Jr. 2018-11-07 21:09:13 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.