Posted by: Anonymous Coward
on October 20, 2005 12:36 AM
Authentication is an important part of any proxy server. Using authentication, many proxy servers allow you to control access to the internet and to specific URLs based on user or group membership. So the ability to integrate Squid authentication with existing directories is critical in most businesses. Most business users are accustomed to opening their browser and having access without being prompted for a user ID and password which means that squid must somehow integrate with the underlying OS of the client, which further complicates the issue. No one wants to have to enter their user ID and password every time they open up a browser.
Unfortunately, the article chose only to use NCSA authentication, which no one uses, as an example. The article would have been much better and more poignant if it had used authentication against a more common directory such as Open LDAP, Active Directory, eDirectory, backend. It would have been even more helpful if it discussed some means of automating the client authentication process so that users are not prompted for user ID and password every time they open a browser.
I think these things are possible with squid but, I certainly wouldn't know that from the article.
Authentication.
Posted by: Anonymous Coward on October 20, 2005 12:36 AMUnfortunately, the article chose only to use NCSA authentication, which no one uses, as an example. The article would have been much better and more poignant if it had used authentication against a more common directory such as Open LDAP, Active Directory, eDirectory, backend. It would have been even more helpful if it discussed some means of automating the client authentication process so that users are not prompted for user ID and password every time they open a browser.
I think these things are possible with squid but, I certainly wouldn't know that from the article.
#