> Yes. Multiple authentication methods, triggered from multiple sources,
> going via multiple paths can be confusing.
>
> Squid auth_param elided, which leaves:
>
> "A user name and password are being requested by ..."
> == basic challenge by ISA.
>
> "Enter user name and password for ..."
>> > That's terrific that it works, but I'm not sure I understand why.
>> Does "connection-auth=off" disable pass-through of NTLM? My
>> understanding of the Activesync devices is that they require NTLM.
>> >
>>
>> Yes it disables pass-thru for NTLM.
>>
>> Which for you blocks that first NTLM chall
> > That's terrific that it works, but I'm not sure I understand why.
> Does "connection-auth=off" disable pass-through of NTLM? My
> understanding of the Activesync devices is that they require NTLM.
> >
>
> Yes it disables pass-thru for NTLM.
>
> Which for you blocks that first NTLM challenge (
Alan Lehman wrote:
Try some of the settings to disable pass-thru on the specific
ports
and/or peer:
http://wiki.squid-cache.org/Features/ConnPin
My config pretty much follows the wiki example for OWA accelerator.
Squid 3.1.0.3. I'm using the same port for OWA and Activesync. I
just
added c
> Try some of the settings to disable pass-thru on the specific
> ports
> and/or peer:
>
> http://wiki.squid-cache.org/Features/ConnPin
> >>>
> >>> My config pretty much follows the wiki example for OWA accelerator.
> >> Squid 3.1.0.3. I'm using the same port for OWA and Actives
Alan Lehman wrote:
The order in which our auth_param lines are configured can alter
the
first authentication method tried. You will need to look at the
debugging trace in cache.log to see which is generating which
question
Amos
Only basic is enabled:
auth_param basic children 5
auth_param ba
> The order in which our auth_param lines are configured can alter
> the
> first authentication method tried. You will need to look at the
> debugging trace in cache.log to see which is generating which
> >> question
> Amos
> >>> Only basic is enabled:
> >>> auth_param basic chi
Alan Lehman wrote:
The order in which our auth_param lines are configured can alter the
first authentication method tried. You will need to look at the
debugging trace in cache.log to see which is generating which
question
Amos
Only basic is enabled:
auth_param basic children 5
auth_param basi
> >> The order in which our auth_param lines are configured can alter the
> >> first authentication method tried. You will need to look at the
> >> debugging trace in cache.log to see which is generating which
> question
> >>
> >> Amos
> >
> > Only basic is enabled:
> > auth_param basic children 5
Alan Lehman wrote:
The order in which our auth_param lines are configured can alter the
first authentication method tried. You will need to look at the
debugging trace in cache.log to see which is generating which question
Amos
Only basic is enabled:
auth_param basic children 5
auth_param ba
Alan Lehman wrote:
The order in which our auth_param lines are configured can alter the
first authentication method tried. You will need to look at the
debugging trace in cache.log to see which is generating which question
Amos
Only basic is enabled:
auth_param basic children 5
auth_param ba
> The order in which our auth_param lines are configured can alter the
> first authentication method tried. You will need to look at the
> debugging trace in cache.log to see which is generating which question
>
> Amos
Only basic is enabled:
auth_param basic children 5
auth_param basic realm Sq
Alan Lehman wrote:
Running 3.0 my accelerator for OWA works fine.
The browser user authentication prompt is "A user name and password are
being requested by ..."
The same configuration on 2.6STABLE6 or 3.1.0.3 -
The browser authentication prompt is now different: "Enter user name and
password
13 matches
Mail list logo
