I'm using application which uses https protocol by Squid 3.5.20 and
It often occurs application timeout and other problems to use this
software.
I tried to use application without Squid, bypassing it, and
It works fine.
How can I find out where Squid could create problems to
this application?
I'm thinking to implement Basic authentication for all clients
because it's easier with my outdated systems.
In squid.conf can I use
one of these three access methods for http_access for each_client?
1-
only based on AD user authentication
2- only based on IP address
3- both
based both on AD us
d Win10 clients anyway
For Windows 7/10 clients, the Basic authentication (Squid 2.7) with
LDAP helper will not able to work ?
While Kerberos will work both with older clients and newer ones?
Il 02.05.2016 13:43 Amos Jeffries ha scritto:
On 2/05/2016 6:39 p.m., Sampei wrote:
I'm goin
Squid is running on old Linux fedora server
Il 02.05.2016 13:43 Amos Jeffries ha scritto:
On 2/05/2016 6:39 p.m., Sampei wrote:
I'm going to configure Squid 2.7 Stable3 to authenticate clients
(Windows XP/7/10) in Active Directory environment (Windows 2000
server).
You have my
I'm going to configure Squid 2.7 Stable3 to authenticate clients
(Windows XP/7/10) in Active Directory environment (Windows 2000 server).
I used directive "auth_param basic program /usr/lib/squid/ldap_auth -v3
..." but I read basic authentication is extremely weak and It transmits
user passwords
