hc-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kwri...@apache.org
Subject svn commit: r1421863 - /httpcomponents/httpclient/trunk/src/site/apt/ntlm.apt
Date Fri, 14 Dec 2012 13:53:45 GMT
Author: kwright
Date: Fri Dec 14 13:53:44 2012
New Revision: 1421863

URL: http://svn.apache.org/viewvc?rev=1421863&view=rev
Update NTLM documentation.


Modified: httpcomponents/httpclient/trunk/src/site/apt/ntlm.apt
URL: http://svn.apache.org/viewvc/httpcomponents/httpclient/trunk/src/site/apt/ntlm.apt?rev=1421863&r1=1421862&r2=1421863&view=diff
--- httpcomponents/httpclient/trunk/src/site/apt/ntlm.apt (original)
+++ httpcomponents/httpclient/trunk/src/site/apt/ntlm.apt Fri Dec 14 13:53:44 2012
@@ -47,11 +47,25 @@ NTLM support in HttpClient
     Principles initiative}}. 
-    HttpClient as of version 4.1 supports NTLMv1 and NTLMv2 authentication protocols out

-    of the box using a custom authentication engine. However, there are still known compatibility
-    issues with newer Microsoft products as the default NTLM engine implementation is still

-    relatively new. One can also use {{{http://jcifs.samba.org/}JCIFS}} as an alternative,
-    established and mature NTLM engine developed by Samba project. 
+    HttpClient as of version 4.1 initially supported NTLMv1, NTLMv2, and NTLM2SessionResponse
+    authentication protocols, based on the reverse engineering approach.  As of version
+    4.2.3, HttpClient now supports a more correct implementation, based in large part on
+    Microsoft's own specifications.  This is expected to correct a number of problems, especially
+    since Microsoft (as of Windows Server 2008 R2) began using a new implementation of its
+    protocols.  This new Microsoft implementation has led to authentication failures in some
+    cases from some of the older reverse-engineered client implementations of NTLM.
+    The new HttpClient NTLM implementation is known to have been tried successfully against
+    at least the following systems:
+    * Windows Server 2000 and Server 2003 systems, configured to use LM and NTLMv1 authentication
+    * Windows Server 2003 systems, configured to use NTLMv2 authentication
+    * Windows Server 2008 R2 systems, configured to use NTLM2SessionResponse authentication
+    If the current HttpClient NTLM implementation should prove problematic in your environment,
+    we'd definitely like to hear about it.  You are also welcome to try an alternative NTLM
+    implementation, should it seem necessary. One can also use {{{http://jcifs.samba.org/}JCIFS}},
+    which includes an NTLM engine developed by members of the Samba project. 
 * {Using Samba JCIFS as an alternative NTLM engine}

View raw message