>
> I have my ACLs based off what group an individual belongs to in a
> LDAP
> tree.
>
> Perhaps something like that would be helpful in your setup.
>
> -Dan
> ___
Thank you
If you have an example, I would be happy to look into
Fred
___
On 11/07/2016 03:19 AM, FredB wrote:
>
>> Use "login=PASS" (exact string) on the cache_peer.
>>
>> Along with an http_access check that uses an external ACL helper
>> which
>> produces "OK user=X password=Y" for whatever credentials need to be
>> sent.
>>
>> NP: on older Squid that may be "pass=
> Use "login=PASS" (exact string) on the cache_peer.
>
> Along with an http_access check that uses an external ACL helper
> which
> produces "OK user=X password=Y" for whatever credentials need to be
> sent.
>
> NP: on older Squid that may be "pass=" instead of "password=".
>
> Amos
>
Ok tha
On 4/11/2016 4:25 a.m., FredB wrote:
>
>> Authentication credentials represent and verify the identity of your
>> proxy. That is a fixed thing so why would the credentials used to
>> verify
>> that static identity need to change?
>
>
> I'm only speaking about users identities, not something like
> Authentication credentials represent and verify the identity of your
> proxy. That is a fixed thing so why would the credentials used to
> verify
> that static identity need to change?
I'm only speaking about users identities, not something like cache_peer
login=XXX
So each user must have is
On 3/11/2016 9:47 p.m., FredB wrote:
> Hello,
>
> I wonder if Squid can pass different login/password to another, depending to
> an ACL ?
> I mean:
>
> 1) a client connected to Squid without any identification helper like ntlm,
> basic, etc ...
> 2) an ACL like IP src, or browser, header, ...
Hello,
I wonder if Squid can pass different login/password to another, depending to an
ACL ?
I mean:
1) a client connected to Squid without any identification helper like ntlm,
basic, etc ...
2) an ACL like IP src, or browser, header, ... forward the request to an
another squid with a login/p
