I use Directory. This is how my config file look like....
<Directory />
AuthType Basic
AuthName "Enter your ID"
AuthBasicProvider ldap
AuthBasicAuthoritative off
AuthLDAPUrl
ldap://url:389/dc=domain,dc=com?samAccountName?sub?(objectClass=*)
NONE
AuthLDAPBindDN "cn=xxx,ou=xxx,dc=domain,dc=com"
AuthLDAPBindPassword xxxxxxxxx
Require valid-user
</Directory>
On Sun, Dec 15, 2013 at 9:12 PM, Eric Covener <cove...@gmail.com> wrote:
> On Sun, Dec 15, 2013 at 9:54 AM, Ramesh Nadupalli
> <nadupalliram...@gmail.com> wrote:
>> Thanks Eric for your response. I have tried below options,
>>
>> Require valid-user (when I pass valid-user, it authenticates
>> and allows everyone in the LDAP filter to access the webserver)
>> Require user usera userb userc (It allows only these users)
>>
>> Since our requirement is to control access based on a path, I am not
>> sure what else can be used to read an access file.
>
> Enclose the directives in <Location> or <Directory>?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
