I am not sure myself not having played with Patchlink Distribution Point or Lumension Caching Proxy (Squid) for some time but the EMSS Agent policy settings for the proxy "fastpath" have an authenticated check box which allows you to enter credentials for the proxy server. Once this policy has been updated on the endpoints they should be able to authenticate on the proxy.
Thanks for the reply. I know that side of it, but the question is how to get the caching proxy to require credentials for the agents as per the policy. No one seems to know how to do that. If I could ditch the caching proxy and get regular squid to work then I know how to configure authentication on that. If I can get it to work I'll publish a tech note on it. Only $5 a copy. A bargain considering how long it takes to figure out on your own.
Sent from my iPhone
Please do share your tech notes on the standard Squid authenticated proxy set up as I am sure this is something many people would be interested in. I can't see why it shouldn't work.
1 of 1 people found this helpful
I'm been working with PatchLink/Lumension/HEAT for over 10 years now and with confidence, I know how to configure Squid Proxy for Windows to force a userID and password. We do not publish these instructions because the userid and password that is sent to the proxy server is sent over clear text so we try and avoid it as much as possible for security reasons.
The official Squid documentation can be found on http://www.squid-cache.org/Doc/config/auth_param/. If you need some documentation from HEAT with reference to our Caching Proxy on Windows let me know.
René Anthony Gonzalez, Sr. Pre-Sales Technical Consultant-Team Lead
O : 480.663.8780 | Email: firstname.lastname@example.org | Skype: rene.gonzalez7
HEAT Software (Lumension is now part of the HEAT Software group)
8660 E. Hartford Dr. Suite 300 | Scottsdale, AZ 85255