On 09/17/2010 03:28 PM, Amos Jeffries wrote:
Squid does not currently offer any way to selectively pick the auth
methods to advertise. There are a few possible designs and someone was
working on it a while back.
Offering a specific authentication method for a defined network would be
a nice fea
Perhaps you could install a separate squid at their sites, which in turn,
routes through yours, dependant on the "inter-networking" topology between
sites?
-
Chad E. Naugle
Tech Support II, x. 7981
Travel Impressions, Ltd.
>>> Amos Jeffries 9/17/2
On 18/09/10 00:14, guest01 wrote:
Hi,
I am stuck with a similar problem, has there been any solution for
this topic? (Btw, I am running Squid 3.1.8 on RHEL5.5)
We are trying to achieve following:
CompanyA (us): own Active Directory domain and we are hosting the
squid web server (central forward
Hi,
I am stuck with a similar problem, has there been any solution for
this topic? (Btw, I am running Squid 3.1.8 on RHEL5.5)
We are trying to achieve following:
CompanyA (us): own Active Directory domain and we are hosting the
squid web server (central forward proxy for internet access with ICAP
Hi
I run squid with the named debug-options. The "cache.log"-output seems
a little bit complicated. So the only way I see, is to have a remarked
native ldap-authentication-configuration, which I can enable, if the
kerberos-mechanism fails.
Or does somebody has such a config (kerberos with squid_k
Tom Tux wrote:
Hi Amos
Thanks a lot for this explanation. Both configurations seperately -
native kerberos and native ldap - are working fine. But in
combination, there is still one problem.
Here is my actual configuration (combined two mechanism) again:
auth_param negotiate program /usr/local
Hi Amos
Thanks a lot for this explanation. Both configurations seperately -
native kerberos and native ldap - are working fine. But in
combination, there is still one problem.
Here is my actual configuration (combined two mechanism) again:
auth_param negotiate program /usr/local/squid/libexec/sq
Tom Tux wrote:
Hi Markus
Thank you.
So, do you know, how I have to implement the fallback-mechnism with
squid_ldap_auth?
You already configured it.
When challenging for credentials Squid sends a list of the supported
authentication protocols. One entry for each auth_param type configured.
I
Hi Markus
Thank you.
So, do you know, how I have to implement the fallback-mechnism with
squid_ldap_auth?
For instance, if I deny read-rights for the squid-user to the file
/etc/krb5.keytab, I would expect, that the squid_ldap_auth-mechanism
would authenticate the user with a password-prompt. But
