I'd like to know if the following could be implemented using Squid.
We want to have Squid running on an AIX or Linus box make a call (open
an HTTP connection) to another host for the purpose of passing the userid
and password combination for authentication via the other host. The
authenticating host would pass back to the Squid host whatever was
required (ERR or OK, I believe) via the HTTP connection opened by the
host running Squid. Essentially, the Squid authentication routine will
just call another host via HTTP which will actually do the authentication.
Possible with Squid?
In addition, we want to pass the requested url along with the userid
and password. With the requested url, userid, and password, the
"authenticating" host can determine if the user should be given access
to the requested url and respond to the Squid host authentication routine
with an ERR or OK. This additional feature would allow us to make more
granular decisions about who gets access to what resources (i.e. urls).
Is it possible with Squid to pass more than just userid and password to
the host which will do the actual authentication check?
It appears from the reading that the authentication routine on the
Squid host can only terminate with an ERR or OK response. True?
If not true, what other responses are possible?
Received on Tue Nov 09 1999 - 17:34:05 MST
This archive was generated by hypermail pre-2.1.9 : Wed Apr 09 2008 - 11:57:32 MDT