mån 2007-07-16 klockan 09:43 -0400 skrev Vootla, Bhagwan: > But I am instructed to AVOID putting anything on the client side. To > avoid this, What I was trying to achieve is... Make apache as a secured > web server and perform secured authentication against ldap server, and > then inform squid server that no more authentication is needed for > browsing. Not sure, if this is possible, But trying to explore the > possible ways. This is possible only if the user can be uniquely identified by the IP address. You can then plug in the needed details to Squid via the external_acl_type directive. Using Digest authentication is another option. Reasonably secure, and reasonable support in most browsers. Problem is on the server side where it's not easy to integrate with existing password databases as the proxy never sees the plain-text password.. Regards Henrik
Attachment:
signature.asc
Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signerad meddelandedel
