[
https://issues.apache.org/jira/browse/HTTPCLIENT-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134256#comment-13134256
]
Oleg Kalnichevski commented on HTTPCLIENT-1139:
-----------------------------------------------
Jeff,
I suspect authentication fails because the server also sends a SPNEGO/kerberos
challenge, which takes precedence over NTLM. If the SPNEGO auth scheme fails
NTLM authentication is not attempted due to HTTPCLIENT-1107.
Anyway, please attach wire / context logs of both sessions (successful with
4.0.3 and unsuccessful with 4.1.2).
Oleg
> NTLM Authentication No Longer Working In Latest Release
> -------------------------------------------------------
>
> Key: HTTPCLIENT-1139
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1139
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient
> Affects Versions: 4.1.2
> Environment: testing on Windows x64, using SharePoint 2010 as a test
> server that accepts NTLM auth
> Reporter: Jeff Nadler
> Fix For: 4.1.3
>
>
> Our application has been working fine using NTLM auth with HttpClient for 3
> years. We were most recently on 4.0.3. Upon upgrading to 4.1.2, NTLM
> stopped working.
> I tried both the new for 4.1 built-in NTLM and the "old way" of using JCIFS:
> client.getAuthSchemes().register("ntlm", new NTLMSchemeFactory());
> Using wireshark I can see that NTLM auth is not even attempted using 4.1.2.
> Rolling back to 4.0.3 immediately resolved this problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
