-$Id: HISTORY,v 1.17 2003/05/05 11:39:03 maxcooper Exp $
-$Revision: 1.17 $
-$Date: 2003/05/05 11:39:03 $
+$Id: HISTORY,v 1.18 2003/07/15 10:34:22 maxcooper Exp $
+$Revision: 1.18 $
+$Date: 2003/07/15 10:34:22 $
Security Filter v@PROJECT.VERSION@
changes made for each release.
-Changes since last release:
+Release 1.1-b1, 2003-Jul-15
===========================
* Added support for BASIC authentication scheme.
-$Id: README,v 1.17 2003/05/05 11:39:03 maxcooper Exp $
-$Revision: 1.17 $
-$Date: 2003/05/05 11:39:03 $
+$Id: README,v 1.18 2003/07/15 10:34:21 maxcooper Exp $
+$Revision: 1.18 $
+$Date: 2003/07/15 10:34:21 $
Security Filter v@PROJECT.VERSION@
What's in this package?
-----------------------
-Two example apps demonstrate securityfilter in action:
+Three example apps demonstrate securityfilter in action:
-1. securityfilter-example.war - Basic securityfilter app using native
-securityfilter realm implementation.
+1. securityfilter-example.war - Simple securityfilter app using native
+securityfilter realm implementation and FORM authentication.
2. securityfilter-catalina-example.war - Same as securityfilter-example app with
Tomcat (Catalina) realm implementation and realm adapter class.
-3. Both securityfilter-catalina-example.war and securityfilter-example.war can be run
-in BASIC Authentication mode i.e. is the user will be challenged for credential using
-a basic window pop-up.
+3. securityfilter-basic.war - Simple securityfilter app using native
+securityfilter realm implementation and BASIC authentication.
A securityfilter-blank.war example app is also provided as a skeleton to use to
start a new securityfilter application, or integrate into an existing
the realm-param tag.
4. Specify either BASIC or FORM authentication scheme in auth-method tag of
-securityfilter-config.xml. If you specify BASIC authentication scheme you can still
-specify an application-specific login form page for logging the user in.
+securityfilter-config.xml. If you specify the FORM authentication scheme you will
+need to specify your form-login-page, form-error-page, and form-default-page.
The example apps include web.xml and securityfilter-config.xml file examples.
1. user-data-constraint tags can be included in the config file, but they are
not yet supported (and thus are ignored)
+The following extended features are planned for a future release, but are not
+yet available in current releases:
+
+1. "Remember me" functionality -- a persistent cookie will be used to provide
+persistent login functionality. Currently, a user will be logged out when their
+session expires or if they close their current browser session. By using a
+persistent cookie, a user will be automatically authenticated when they return
+to a site, even if their session expired or if they close their browser in between
+accesses.
+
+2. Application-specific processing at authentication time -- this will allow
+application developers to write code that will be executed when a user is
+authenticated. This is useful for populating the session with user profile
+informtaiton, etc.
+
Contributors
------------
Thank you,
The SecurityFilter Team
-
-
<!--
-$Id: properties.xml,v 1.9 2003/07/07 13:40:40 maxcooper Exp $
-$Revision: 1.9 $
-$Date: 2003/07/07 13:40:40 $
+$Id: properties.xml,v 1.10 2003/07/15 10:34:21 maxcooper Exp $
+$Revision: 1.10 $
+$Date: 2003/07/15 10:34:21 $
-->
<!--
<property name="project.name" value="securityfilter"/>
<!-- default version of this project (override with command line version when building releases) -->
-<property name="project.version" value="1.1-dev"/>
+<property name="project.version" value="1.1-b1"/>
<!-- Should Java compilations set the debug compiler option? -->
<property name="compile.debug" value="true"/>