Re: Authenticating uses on a parent proxy

Well, that depends. Exactly what sort of authentication is it? If it's a
407 proxy-authentication response, then it should work as is. If it's
something else, I guess we'd need to know what _kind_ of something else.

D

Peter Bates wrote:
>
> Our setup is as follows,
> We have our Internet Gateway / Proxy server located at our corporate
> offices. We run Squid 2.2 at our remote site to minimise WAN traffic
> between our remote sites and the Internet gateway in head office. The
> Gateway is running Novell Bordermanager.
>
> I have squid setup with this Novell proxy as its sole parent. This proxy
> should be queried for all requests that are external to our site. From
> looking at the logs this seems to be working.
>
> The problem is this. Novel Proxy needs the clients to provide a username
> and password. If they connect to Novell Bordermanager directly this works
> fine. When they connect to Novell Bordermanager via Squid, they are not
> even asked for a password, and the request is refused by Novel Border
> manager.
>
> How do I get Squid / Novell Bordermanager to corretly pass the users name
> and passwrod request back to the client, and they forward the information
> back?
>
> The relevant setup lines are as follows
>
> Note we use the Public A class IP range internaly, and all addresses local
> to the squid proxy are on the 10.1.0.0 subnet
>
> ---------------------------------------------------------------------------
> -------
> cache_peer 10.21.0.45 parent 8080 7 no-query default
>
> acl all_hosts dst 0.0.0.0/0.0.0.0
> acl all_clients src 0.0.0.0/0.0.0.0
> acl ampol_host dst 10.0.0.0/255.0.0.0
>
> http_access allow all_clients
>
> never_direct deny ampol_hosts
> never_direct allow all_hosts
> ---------------------------------------------------------------------------
> ----
>
> What do I have to add to this?
Received on Wed Jun 02 1999 - 17:27:33 MDT