Summary: | Prepend and append string to LDAP search parameter | ||
---|---|---|---|
Product: | Apache httpd-2 | Reporter: | Steve Cross <hairlesshobo> |
Component: | mod_auth_ldap | Assignee: | Apache HTTPD Bugs Mailing List <bugs> |
Status: | RESOLVED LATER | ||
Severity: | enhancement | Keywords: | MassUpdate, PatchAvailable |
Priority: | P2 | ||
Version: | 2.2.17 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Attachments: | Patch to mod_authnz_ldap that allows a string to be appended and prepended to the search parameter |
Description
Steve Cross
2011-06-04 23:06:04 UTC
I have created a patch that adds the following two options to the mod_authnz_ldap configuration: AuthLDAPAttrPrependString AuthLDAPAttrAppendString These two configuration parameters allow you to specify a string that must be added before and after the LDAP value that is being searched for. Using the example structure in the post above, if someone were to login with the username "johndoe", then it would be searching the LDAP database for that exact cn. Now configure the module with the following line: AuthLDAPAttrPrependString "example.org_" When configured this way and someone logs in with the username "johndoe", the LDAP database is searched for "example.org_johndoe" instead. I have attached the patch which was originally written for 2.2.16 but has been tested against the latest stable 2.2.19 version. Steve Cross Created attachment 27112 [details]
Patch to mod_authnz_ldap that allows a string to be appended and prepended to the search parameter
Standard unified diff format.
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. |