On Thursday, January 13, 2011 01:38:54 pm Eric Covener wrote: > On Thu, Jan 13, 2011 at 3:16 AM, Sebastian Reitenbach > > <sebastia@xxxxxxxxxxxxxxxxxxxx> wrote: > > On Tuesday, January 11, 2011 02:38:31 pm Eric Covener wrote: > >> > Or on the other hand, is it possible to tell mod_authnz_ldap to bind > >> > as the user instead of anonymous to make the compare request? > >> > >> The manual tells you how to use a userid/password. > > > > I rechecked the documentation, and I found the following directives in > > the apache-trunk documentation: > > AuthLDAPSearchAsUser > > AuthLDAPCompareAsUser > > > > which is probably what I want, since I don't really want to hardcode a > > BindDN and BindPassword in the apache configuration.. > > > > I have apache-2.2.15, and checked the changelog of up to apache-2.2.17, > > and as it seems, those directives are not yet there. The docs says, its > > only available since 2.3.6. > > > > Or did you have other configuration directives in mind? > > I meant the bind DN and password, not the trunk features. > Ah, OK, yes, with the bindDN I also found it working, and its fine for my testing purposes, I don't want to put username/passwords into configuration files on the server. In the meantime I opened a service request at IBM so that they may hopefully tell me how to enable anonymous compare on the LDAP service, since I haven't found a hint on it in the IBM documentation. Even the guy on the phone was a bit unsure about the issue ;) Its not a too urgent issue for me, either I get a sufficient answer from IBM, or I'll wait for future apache. Just wanted to make sure I don't overlook something. Thanks to everyone. Sebastian --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|