You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Graham Leggett <mi...@sharp.fm> on 2006/11/29 12:30:49 UTC

Auth in Location: can one basic auth config override another?

Hi all,

After much experimentation with httpd v2.0, where an attempt is made to
set one basic auth policy for Location /, and a different basic auth
policy for Location /bugzilla, it seems that regardless of the order of
the Location in the config file, the most general config always wins.

In other words, it seems currently to be impossible to define a different
basic auth config in a subdirectory in an urlspace, if an existing more
general basic auth config exists for a parent directory.

Can anyone who knows the AAA stuff better confirm whether this is true or
not?

Regards,
Graham
--



Re: Auth in Location: can one basic auth config override another?

Posted by Plüm, Rüdiger, VF EITO <ru...@vodafone.com>.

> -----Ursprüngliche Nachricht-----
> Von: Graham Leggett
> Gesendet: Mittwoch, 29. November 2006 13:31
> 
> Which version of httpd are you using?

2.0.55

> 
> 
> In my case, I am trying to define one basic auth config under / using
> mod_authz_ldap, and a second completely separate and independent basic
> auth config /bugzilla using mod_auth_ldap (note the different 
> modules).
> This doesn't want to work.

Ok, this is different from my case. I only have different realms and requires.

Regards

Rüdiger


Re: Auth in Location: can one basic auth config override another?

Posted by Graham Leggett <mi...@sharp.fm>.
On Wed, November 29, 2006 1:59 pm, Plüm, Rüdiger, VF EITO wrote:

> I don't think so. I have the following configuration running successfully:
>
> <Location /somewhere>
>    Options None
>    AllowOverride None
>    DAV On
>    AuthName "Access for somewhere"
>    AuthType Basic
>    AuthUserFile /opt/apache-2.0.55/conf/transfer/passwd.manager
>
>    order allow,deny
>    allow from all
>    Satisfy all
>
>    Options none
>    ForceType application/octet-stream
>
>  <LimitExcept OPTIONS>
>    require user manager
>  </LimitExcept>
> </Location>
>
> <Location /somewhere/deeper/evendeeper>
>    AuthName "Access for evendeeper"
>
>  <LimitExcept OPTIONS>
>    require user manager somebodyelse
>  </LimitExcept>
> </Location>
>
> If I go to /somewhere/deeper/evendeeper I get the correct Realm presented
> in the browser.

Which version of httpd are you using?

In the case quoted above, both /somewhere and /somewhere/deeper/evendeeper
are using the same basic auth config - the difference being in authz
(require).

In my case, I am trying to define one basic auth config under / using
mod_authz_ldap, and a second completely separate and independent basic
auth config /bugzilla using mod_auth_ldap (note the different modules).
This doesn't want to work.

Regards,
Graham
--



Re: Auth in Location: can one basic auth config override another?

Posted by Plüm, Rüdiger, VF EITO <ru...@vodafone.com>.

> -----Ursprüngliche Nachricht-----
> Von: Graham Leggett 
> Gesendet: Mittwoch, 29. November 2006 12:31
> An: dev@httpd.apache.org
> Betreff: Auth in Location: can one basic auth config override another?
> 
> 
> Hi all,
> 
> After much experimentation with httpd v2.0, where an attempt 
> is made to
> set one basic auth policy for Location /, and a different basic auth
> policy for Location /bugzilla, it seems that regardless of 
> the order of
> the Location in the config file, the most general config always wins.
> 
> In other words, it seems currently to be impossible to define 
> a different
> basic auth config in a subdirectory in an urlspace, if an 
> existing more
> general basic auth config exists for a parent directory.
> 
> Can anyone who knows the AAA stuff better confirm whether 
> this is true or
> not?

I don't think so. I have the following configuration running successfully:

<Location /somewhere>
   Options None
   AllowOverride None
   DAV On
   AuthName "Access for somewhere"
   AuthType Basic
   AuthUserFile /opt/apache-2.0.55/conf/transfer/passwd.manager

   order allow,deny
   allow from all
   Satisfy all

   Options none
   ForceType application/octet-stream

 <LimitExcept OPTIONS>
   require user manager
 </LimitExcept>
</Location>

<Location /somewhere/deeper/evendeeper>
   AuthName "Access for evendeeper"
   
 <LimitExcept OPTIONS>
   require user manager somebodyelse
 </LimitExcept>
</Location>

If I go to /somewhere/deeper/evendeeper I get the correct Realm presented in the browser.

Regards

Rüdiger