Hi Amos and Dima,
I'm having the exact same problem. After updating Chrome to version (47.0.2526.73 m) I'm no longer able to authenticate. IE and Firefox still seem to work fine. I haven't changed anything in my config file for months.
On Fri, Dec 4, 2015 at 5:22 AM, Dima Ermakov <demonihin@xxxxxxxxx> wrote:
My clients with problems has google chrome v47 (((Ten minutes ago "Noel Kelly nkelly@xxxxxxxxxxxxxxxxxx" wrote in this list, that google chrome v47 has broken NTLM authentication.I didn't change my configuration more than one month.Before 2015-12-03 all was good.I have this problem only on google chrome browser.It didn't help me.Thank you, Amos.I checked all, that you wrote.Mozilla Firefox clients work good.Thank you!This is message from Noel Kelly:
"
Hi
For information, the latest version of Google Chrome (v47.0.2526.73M) has broken NTLM authentication:
https://code.google.com/p/chromium/issues/detail?id=544255
https://productforums.google.com/forum/#!topic/chrome/G_9eXH9c_ns;context-place=forum/chrome
Cheers
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
"--On 4 December 2015 at 04:55, Amos Jeffries <squid3@xxxxxxxxxxxxx> wrote:On 4/12/2015 9:46 a.m., Dima Ermakov wrote:
> Hi!
> I have a problem with authentiation.
>
> I use samba ntlm authentication in my network.
>
> Some users ( not all ) have problems with http traffic.
>
> They see basic authentication request.
Meaning you *dont* have NTLM authentication on your network.
Or you are making the mistake of thinking a popup means Basic
authentication.
> If they enter correct domain login and password, they have auth error.
> If this users try to open https sites: all works good, they have not any
> type of errors.
So,
a) they are probably not going through this proxy, or
b) the browser is suppressing the proxy-auth popups, or
c) the authentication request is not coming from *your* proxy.
>
> So we have errors only with unencrypted connections.
>
> I have this error on two servers:
> debian8, squid3.4 (from repository)
> CentOS7, squid3.3.8 (from repository).
>
Two things to try:
1) Adding a line like this before the group access controls in
frntend.conf. This will ensure that authentiation credentials are valid
before doing group lookups:
http_access deny !AuthorizedUsers
2) checking up on the Debian winbind issue mentioned in
<http://wiki.squid-cache.org/ConfigExamples/Authenticate/Ntlm#winbind_privileged_pipe_permissions>
Im not sure about this it is likely to be involved on Debian, but CentOS
is not known to have that issue.
Oh and:
3) remove the "acl manager" line from squid.conf.
4) change your cachemgr_passwd. Commenting it out does not hide it from
view when you post it on this public mailing list.
You should remove all the commented out directives as well, some of them
may be leading to misunderstanding of what the config is actually doing.
Amos
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
С уважением, Дмитрий Ермаков.
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
Samuel Anderson | System Administrator | International Document Services
![]()
IDS | 11629 South 700 East, Suite 200 | Draper, UT 84020-4607
CONFIDENTIALITY NOTICE:
This e-mail and any attachments are confidential. If you are not an intended recipient, please contact the sender to report the error and delete all copies of this message from your system. Any unauthorized review, use, disclosure or distribution is prohibited.
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
