Feature #1248
closedAllow User-DN to be supplied in the configuration rather than searching
Description
Right now, every connection requires an anonymous (or bound) connection used to search the user-dn. Rather than searching for the user-dn, it should be possible to define the user-dn in the configuration file.
-- douglas
Files
Updated by Anonymous over 17 years ago
I'm not sure if it was clear from reading my comments, but the first two patches (the first of which can be ignored) are against the 1.4.x branch. The third and final patch is against the trunk.
-- douglas
Updated by deepunix over 17 years ago
This ticket would be a good place for adding patches to mod_auth's ldap code ;)
Here is my patch against 1.4.16 that adds possibility to set dereference option. The option is set every time user is authenticating. It works, but needs some testing.
It's enabled by adding to config file the following line:
auth.backend.ldap.deref = "always" # can be always, find, search or never
Douglas, maybe you could integrate this into your patch ? :)
Updated by gstrauss about 8 years ago
- Description updated (diff)
- Status changed from New to Need Feedback
Is there still interest in allowing User-DN to be supplied in the configuration rather than searching?
Separately, is there interest in deepunix dereference option (which was inappropriately posted to this ticket)?
Updated by gstrauss about 8 years ago
Perhaps a specially-formated auth.backend.ldap.filter that begins with ',' could indicate that there is no need for a query and to simply concatenate uid=<username> to the 'filter' to form the DN.
Updated by gstrauss about 8 years ago
- Status changed from Need Feedback to Fixed
- % Done changed from 0 to 100
Applied in changeset 8b282db1d15e11655b1d7f69dc7cb9ceeba3bcbf.
Also available in: Atom