[
https://issues.apache.org/jira/browse/HTTPCLIENT-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837709#action_12837709
]
Karl Wright commented on HTTPCLIENT-919:
----------------------------------------
Hi all,
Lack of native NTLM support in 4.x also may block Lucene Connector Framework
from using 4.x. This is because many of its connectors require NTLM.
HttpClient 4.x's solution requires jcifs, and jcifs is a LGPL-licensed
component, which means we cannot distribute it according to Apache rules.
The submitted patch has been granted to ASF officially to Apache as part of the
software grant for LCF, and thus it can form the basis of a full featured NTLM
implementation in HttpClient, which we feel would be highly desirable for the
above reason.
> NTLM implementation lacks support for NTLMv1, NTLMv2, and NTLM2 Session forms
> of NTLM
> -------------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-919
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-919
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Reporter: Karl Wright
> Attachments: ntlmv2-etc.patch
>
>
> The current HttpClient implementation lacks support for all enhancements to
> NTLM after Windows 95. That includes NTLMv1, NTLMv2, and NTLM2 Session
> Response varieties of the protocol.
> This seriously impacts the usability of HttpClient in enterprise situations,
> which has required the Lucene Connector Framework team to extend HttpClient
> to address the issue.
> I've attached a patch which contains the implementation used by LCF.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
