[
https://issues.apache.org/jira/browse/HTTPCLIENT-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922078#action_12922078
]
Karl Wright commented on HTTPCLIENT-919:
----------------------------------------
That's great news!
If the authentication architecture is at all similar, it should not take me too
long to do this. The logic trickiness is in all the encryption, and perhaps in
getting some DC's set up with the proper switches for testing. But I won't be
able to start on it for a couple of weeks at best. But by then I am hoping to
have procured access to my old testing environment formerly at MetaCarta and
now at qBase, so that I can verify the code.
If your time frame is too urgent for that, then by all means I urge you to go
ahead.
> 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
> Components: HttpAuth
> Reporter: Karl Wright
> Fix For: 4.1 Alpha3
>
> 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]
