On 08/12/2009 07:49 PM, Igor Cicimov wrote:
As far as I know the Location is used for file system that doesn't
reside on the local server (e.g. proxy server) and Directory in case
you want to protect file system that is local to the server.
No, Location refers to the request's URL while Direct
The folders I'm publishing are not coming from a single source tree on
the filesystem. For instance /www/htdocs is the root of my webserver
while Trac is installed in /raid/trac and the wiki comes
from /raid/wiki. My understanding is that if I'm using Directory I need
to secure a common root on th
Good work Nico. Just out of curiosity, why did you use Location statement
instead Directory in your configuration? As far as I know the Location is
used for file system that doesn't reside on the local server (e.g. proxy
server) and Directory in case you want to protect file system that is local
to
Found it. I was mixing Location and Directory directives. The following
does exactly what I want:
Allow from all
AuthzLDAPAuthoritative on
AuthBasicProvider ldap
AuthName "xxx"
AuthType Basic
AuthLDAPBindDN
AuthLDAPBin
To answer my own questions partially:
- yes it's possible to turn on authentication for the whole server by
creating a section and putting the Auth... statements in
there. Unfortunately I'm unable to require different types of
authentication in different parts of the site. If I put 'require
vali
Hi,
I have an internal apache 2.2 server that serves a number of
applications (trac, subversion, twiki, ...). Every application on the
webserver requires LDAP authentication. To do this I added a
'AuthLDAP...' sections to each '' section in the apache config
files. Unfortunately this means:
