From: markt
Date: Mon, 28 Mar 2011 08:49:49 +0000 (+0000)
Subject: Update based on feedback
X-Git-Url: https://git.internetallee.de/?a=commitdiff_plain;h=81e20934bb2f6b5204c4af1732e39efa96f344d3;p=tomcat7.0
Update based on feedback
Fix typos
git-svn-id: https://svn.apache.org/repos/asf/tomcat/trunk@1086158 13f79535-47bb-0310-9956-ffa450edef68
---
diff --git a/webapps/docs/windows-auth-howto.xml b/webapps/docs/windows-auth-howto.xml
index 914eb05f3..28fc4a866 100644
--- a/webapps/docs/windows-auth-howto.xml
+++ b/webapps/docs/windows-auth-howto.xml
@@ -35,7 +35,7 @@
Integrated Windows authentication is most frequently used within intranet
environments since it requires that the server performing the authentication and
-the user being authentication are part of the same domain. For the user to be
+the user being authenticated are part of the same domain. For the user to be
authenticated automatically, the client machine used by the user must also be
part of the domain.
There are several options for implementing integrated Windows authentication
@@ -57,17 +57,28 @@ sections.
- Full details of this solution can be found on the
- Waffle site. The edited highlights
- are:
+
Full details of this solution can be found through the
+ Waffle site. The key features are:
- Drop-in solution
- Simple configuration (no JAAS or Kerberos keytab configuration required)
+ - Uses a native library
+
+ Full details of this solution can be found through the
+
+ Kerberos extension site. The key features are:
+
+ - Extension to Spring Security
+ - Requires a Kerberos keytab file to be generated
+ - Pure Java solution
+
+
+
@@ -92,11 +103,11 @@ sections.
there are a number of third-party modules that can be used. These include:
- mod_auth_sspi
- for use on Windows platforms
- - mod_ntlm for non-Windows
- platforms (NTLM v1 only)
+ for use on Windows platforms.
-
- mod_auth_ntlm_winbind for non-Windows platforms (NTLM v2)
+ mod_auth_ntlm_winbind for non-Windows platforms. Known to work with httpd
+ 2.0.x on 32-bit platforms. Some users have reported stability issues with both
+ httpd 2.2.x builds and 64-bit Linux builds.
There are three steps to configuring httpd to provide Windows
authentication. They are: