On Thu, Mar 22, 2012 at 2:03 PM, Eric Covener wrote:
>> So, how to supply the information parsed from the URI as part of the
>> argument to the require ldap-group directive *at REQUEST time*. Is
>> that %{xxx} resolution something that takes place at the time the
>> r
> So, how to supply the information parsed from the URI as part of the
> argument to the require ldap-group directive *at REQUEST time*. Is
> that %{xxx} resolution something that takes place at the time the
> request is being serviced and honored, or is it something t
J.Lance Wilkinson wrote:
I don't believe I ever got a reply to this, so since it's been a month I'll
repeat it...
the story so far: I have a need to be able to parse into an
environment variable (using Rewrite rules or some such) a value
that then can be used in a *require* directiv
I don't believe I ever got a reply to this, so since it's been a month I'll
repeat it...
the story so far: I have a need to be able to parse into an
environment variable (using Rewrite rules or some such) a value
that then can be used in a *require* directive like
Eric Covener wrote:
LDAP attributes can be loaded into AUTHENTICATE_* vars and can be
queried, but you might not be able to express the rules you need using
attributes only.
Not sure exactly what you're saying here... "AUTHENTICATE_* vars"
are those environment variables or som
On Fri, Feb 24, 2012 at 8:59 AM, J.Lance Wilkinson wrote:
> Eric Covener wrote:
>>
>> IIRC, there was a patch contributed that allowed the filter to be set
>> dynamically [but not the require]. Might turn something up in
>> bugzilla.
>
>
> Shoot. Don't really like to be selectively patchin
Eric Covener wrote:
IIRC, there was a patch contributed that allowed the filter to be set
dynamically [but not the require]. Might turn something up in
bugzilla.
Shoot. Don't really like to be selectively patching things
like that. But will look into it. Setting the filter dy
IIRC, there was a patch contributed that allowed the filter to be set
dynamically [but not the require]. Might turn something up in
bugzilla.
-
The official User-To-User support forum of the Apache HTTP Server Project.
See http://
I'd said:
>
> I'm presuming that there's some way, using a mod_rewrite rule, to
> extract the desired information from the URI and stash it, say, in
> an environment variable. The task then is to somehow use that
> extracted value to impose the appropriate restrictions in the
>
Have a look at SetEnvIf and mod_rewrite where you can set enviroment
variable based on something in the headers, uri and/or request string. Not
sure if yo can use that var inside mod_authz_ldap though.
On Feb 24, 2012 5:48 AM, "J.Lance Wilkinson" wrote:
> I've just been asked to implement in Apa
I've just been asked to implement in Apache HTTPD a restricted access area
that drives off membership in an LDAP group.
I have production services running on Solaris 10 using Apache/2.2.6.
Eventually these will be replaced with servers running on RHEL 6 using
Apache/2.2.15, but that's not likel
11 matches
Mail list logo
