On 4/06/19 11:27 am, Ilias Clifton wrote: >>>>>> Sent: Wednesday, May 29 2019 6:42 >>>>>> From: Ilias Clifton >>>>>> >>>>>> I have Squid 3.5.27 running on Ubuntu 18.04.2, and have been unsuccesfull in being able to authenticate users via ldap (kerberos is working well) >>>>>> >>>>>> What else can I do for troubleshooting? >>>>>> >>> >>> What I do is take one of the access.log lines and read through the squid.conf (whole thing) to see what squid would do with that transaction. Most 40* status problems are with http_access ordering, so quickly spotted. >>> >>> If you can provide those details in full im happy to do so for you. Or someone experienced with a similar config may spot the issue. >>> >> >> Sent: Friday, May 31, 2019 at 8:28 AM >> From: "Ilias Clifton" >> >> See squid.conf below.. Any other config files you need to see? > > Would upgrading to a new version of squid help, like 4.6? That is unlikely to make any difference. But since the problem cause is still not properly known I cannot answer that definitively. Did you see my response about your config? It is most probably that whitespace on the auth_param line, or possibly the sequence of auth related ACLs in http_access. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
