From 427854904521b418b8708c3a4cb2db1fbb04fea7 Mon Sep 17 00:00:00 2001
From: dayash <dayash>
Date: Sat, 18 Jan 2003 07:26:16 +0000
Subject: [PATCH] changed the current limitation to read "SecurityFilter only
 supports FORM and BASIC authentication....."

---
 doc/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/index.html b/doc/index.html
index 5050c6c..f62b052 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -52,7 +52,7 @@ SecurityFilter is intended for use by Java web application developers. It provid
 
 <ul>
   <li>SecirityFilter requires a Servlet 2.3 compliant server environment. This includes Tomcat 4+, WebLogic 6.1+, and many other servers. Consult your server documentation to check for Servlet 2.3 support.<p /></li>
-  <li>SecurityFilter only supports FORM based authentication. This is the most popular type of login configuration as it supports an application-specific login form page.<p /></li>
+  <li>SecurityFilter only supports FORM and BASIC authentication. These are the most popular type of login configurations as they support an application-specific login form page and the pop-up window for login.<p /></li>
   <li>&lt;user-data-constraint&gt; elements are allowed in the SecurityFilter configuration file, but they are not currently supported. &lt;user-data-constraint&gt; elements are used to indicate what web resources are to be accessed only via HTTPS. Support for these constraints is expected to be available soon.<p /></li>
   <li>When SecurityFilter is used, a user's Principal will not automatically be propagated to EJB calls. Supporting EJBs with SecurityFilter is currently under investigation, but it is not a currently supported environment.<p /></li>
   <li>Single Sign-On among several web application contexts is not currently supported. We are investigating possible solutions for this configuration.<p /></li>
-- 
2.11.0