Through some help from this list i figured out how to do something similar
just last night.
In squid 3.0 there is the cache_peer option login=PROXYPASS - this option
converts proxy-authorization to http-authorization and then passes it to
the nominated cache_peer.
So what we do is make everyone authenticate to the proxy and then if they
are going to auth.domain they go through cache_peer with login=PROXYPASS
and the auth credentials are passed to the target webpage which can then
use an apache auth or php to allow them access to the requested page. All
requests not destined for auth.domain are passed to a different cache_peer
- they could just go direct - we are using the upstream peer to do content
filtering as the particular content filter software we were forced to use
uses a proprietry Cisco IFP protocol to communicate with caches :(
Not exactly what you are looking for but might help
Cheers
______________________________
David Brown
RHCE MCP CCA
CSM Technology
99 Frome St,
Adelaide SA 5001
Ph: (08) 8418 7804
Fax: (08) 8418 7820
Mob: 0414 494 802
Email: david.brown@csm.com.au
Martyn Bright
<brightm@trml.co.
uk> To
23/09/2004 12:12 cc
AM
Subject
[squid-users] Squid and Apache
Authentication
I would like to be able to use a web page on my Apache server to validate a
users id and password, and then redirect them on to another external site
via a copy of Squid installed on the same machine. I have seen numerous
references to this as a possibility, but can anyone give me confirmation
that it works and what steps I will require to configure it.
Thanks
Martyn Bright
Received on Wed Sep 22 2004 - 17:44:30 MDT
This archive was generated by hypermail pre-2.1.9 : Fri Oct 01 2004 - 12:00:02 MDT