Andreas Sewe created HTTPCLIENT-1488:
----------------------------------------
Summary: Built-in NTLM engine fails to authenticate against Squids
ntlm_fake_auth, JCIFS doesn't
Key: HTTPCLIENT-1488
URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1488
Project: HttpComponents HttpClient
Issue Type: Bug
Components: HttpClient
Affects Versions: 4.3.3
Environment: Squid 4.3.3
JCIFS 1.3.17
Reporter: Andreas Sewe
I used the provided ClientProxyAuthentication example
<https://hc.apache.org/httpcomponents-client-4.2.x/httpclient/examples/org/apache/http/examples/client/ClientProxyAuthentication.java>
to authenticate with NTML against a local Squid instance, using its
ntlm_fake_auth helper (only does the handshake, all credentials are considered
valid).
Unfortunately, this fails with the NTLM engine built into version 4.3.3 (also
tested with 4.2.1: same result). Following the guidance of
<http://hc.apache.org/httpcomponents-client-ga/ntlm.html>, I got it working
with JCIFS. Is Squid not implementing NTLM as expected by HttpComponents?
I added two Wireshark captures to show the differences in handshake behaviour
between the built-in and JCIFS engines. Hope that helps.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
