[
https://issues.apache.org/jira/browse/HTTPCLIENT-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721216#action_12721216 ]
Konstantin Kasatkin commented on HTTPCLIENT-579:
------------------------------------------------
Actually no, because I've had little time to implement the algorithm and there have been no time to add features for seamless switching to different versions NTLM. The original library httpclient has already included NTLMv1 implementation so you can use its implementation for interaction via NTLMv1.
All what you need is to implement a method that could get NTLM version from HTTP request and basing on the result use corresponding authentification algorithm.
> NTLMv2 support
> --------------
>
> Key: HTTPCLIENT-579
> URL:
https://issues.apache.org/jira/browse/HTTPCLIENT-579> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpAuth
> Affects Versions: 3.0 Final
> Environment: WIndows 2000 Pro SP4, JDK 1.4.2
> Reporter: Konstantin Kasatkin
> Fix For: 3.1 Alpha 1
>
> Attachments: ntlmv2-session-security.diff, NTLMv2.rar, NTLMV21.RAR
>
>
> Hello guys,
> recently I've encouner the problem how to interact with HTTP resourses protected tough security policy allowed to use only NTLMv2 authorization scheme from a java application.
> Earlier I used httpclient to accomplish NTLMv1 authorization, but when I was requested to move to NTLMv2 I was surprised, that httpclient does not support this.
> I've dug all the Internet and found some articles and examples how to implement it, and finally having compiled all this enormous heap of information, I have a couple modified classes from httpclient project, that I'd like to share with you and other users of httpclient.
--
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:
dev-unsubscribe@...
For additional commands, e-mail:
dev-help@...
