Search squid archive

Re: Authentication Issue with Squid and mixed BASIC/NTLM auth

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Hey all,
>
>
>
> I've got a tough situation I'm hoping someone can help me with.
>
>
>
> We 'downgraded' from an old 3.0PRE build that a predecessor had setup on a
> reverse proxy, to squid 2.6.STABLE20. The proxy runs your standard OWA
> over Reverse Proxy setup, with login=PASS to an OWA backend running with
> BASIC/NTLM auth. We have to have the NTLM for phones that sync with
> ActiveSync.
>
>
>
> It seems like something fundamental has changed in the way squid handles
> auth from 3.0 to squid 2.6. Using firefox on 2.6, I can auth with just
> 'USERNAME', with IE on 2.6 we have to type "DOMAINUSERNAME" or
> "USER@DOMAIN" now. Previously, with squid 3.0, just 'USERNAME' would work
> for auth.
>
>
>
> While this seems trivial, anything harder than just 'USERNAME' boggles a
> lot of users. I'm assuming this has something to do with 'attempting NTLM'
> negotiation? Is there a way around it in squid 2.6?
>

The cleaner @DOMAIN handling was only added to Squid 2.7+ and 3.0+. You
will need an upgrade again to one of those versions at least.

What caused you to downgrade though? perhapse its been fixed now in 3.1?

Amos


[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux