Perfect!
I just used the line below and it goes fine thru
both proxies, the first proxy do not have any
authentication directives, the parent is doing
authentication thru LDAP.
cache_peer 192.168.1.13 parent 3128 3130 default login=PASS
Many thanks!
--
Bye,
Fernando Maciel Souto Maior
[EMAIL P
On Wed, 5 Nov 2003, Fernando Maior wrote:
> Hmmm,
>
> What I understood from what you wrote, I must have exactly
> the same directives and files for authenticating for both
> squids.
No, not at all.
What you MUST do is to tell each Squid who is to forward the
authentication to a parent proxy t
Hmmm,
What I understood from what you wrote, I must have exactly
the same directives and files for authenticating for both
squids. In this case, both should be authenticating against
LDAP and, also, squid 1 must have the option login=PASS
added to the cache_peer directive.
Will squid do it right
On Tue, 4 Nov 2003, Fernando Maior wrote:
> I did try the following:
>
> user -- squid 1 -- squid 2 -- internet
> \
>ldap
>
> It pops up the authentication window everytime I click in the "OK"
> button, again and again.
You need to tell squid 1 tha
Dear All,
I am running one instance of squid (2.5.STABLE4) that
requires users be authenticated against LDAP. This is
running fine as it should be, for more than six months.
But we are a network of branch offices and now it is
time to bring them together to access internet via
one only connection
