Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@www.apache.org Received: (qmail 11512 invoked from network); 21 Aug 2004 12:38:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 21 Aug 2004 12:38:09 -0000 Received: (qmail 25936 invoked by uid 500); 21 Aug 2004 12:37:58 -0000 Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 25878 invoked by uid 500); 21 Aug 2004 12:37:57 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 25863 invoked by uid 500); 21 Aug 2004 12:37:57 -0000 Received: (qmail 25859 invoked by uid 99); 21 Aug 2004 12:37:57 -0000 X-ASF-Spam-Status: No, hits=-2.8 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [209.237.227.194] (HELO minotaur.apache.org) (209.237.227.194) by apache.org (qpsmtpd/0.27.1) with SMTP; Sat, 21 Aug 2004 05:37:57 -0700 Received: (qmail 11441 invoked by uid 1787); 21 Aug 2004 12:37:56 -0000 Date: 21 Aug 2004 12:37:56 -0000 Message-ID: <20040821123756.11440.qmail@minotaur.apache.org> From: markt@apache.org To: jakarta-tomcat-4.0-cvs@apache.org Subject: cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs realm-howto.xml X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N markt 2004/08/21 05:37:56 Modified: webapps/tomcat-docs realm-howto.xml Log: Fix bug 12516. Clarify that the cached Principal is not retained across session serialisation. Revision Changes Path 1.14 +14 -10 jakarta-tomcat-4.0/webapps/tomcat-docs/realm-howto.xml Index: realm-howto.xml =================================================================== RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/realm-howto.xml,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- realm-howto.xml 4 Sep 2003 19:59:47 -0000 1.13 +++ realm-howto.xml 21 Aug 2004 12:37:56 -0000 1.14 @@ -326,9 +326,10 @@ roles) are cached within Tomcat for the duration of the user's login. (For FORM-based authentication, that means until the session times out or is invalidated; for BASIC authentication, that means until the user - closes their browser). Any changes to the database information for an - already authenticated user will not be reflected until - the next time that user logs on again. + closes their browser). The cached user is not saved and + restored across sessions serialisations. Any changes to the database + information for an already authenticated user will not be + reflected until the next time that user logs on again.

Administering the information in the users and user roles table is the responsibility of your own applications. Tomcat does not provide any built-in capabilities to maintain users and roles.

@@ -499,9 +500,10 @@ roles) are cached within Tomcat for the duration of the user's login. (For FORM-based authentication, that means until the session times out or is invalidated; for BASIC authentication, that means until the user - closes their browser). Any changes to the database information for an - already authenticated user will not be reflected until - the next time that user logs on again. + closes their browser). The cached user is not saved and + restored across sessions serialisations. Any changes to the database + information for an already authenticated user will not be + reflected until the next time that user logs on again.

Administering the information in the users and user roles table is the responsibility of your own applications. Tomcat does not provide any built-in capabilities to maintain users and roles.

@@ -1088,9 +1090,10 @@ roles) are cached within Tomcat for the duration of the user's login. (For FORM-based authentication, that means until the session times out or is invalidated; for BASIC authentication, that means until the user - closes their browser). Any changes to the directory information for an - already authenticated user will not be reflected until - the next time that user logs on again. + closes their browser). The cached user is not saved and + restored across sessions serialisations. Any changes to the directory + information for an already authenticated user will not be + reflected until the next time that user logs on again.

Administering the information in the directory server is the responsibility of your own applications. Tomcat does not provide any built-in capabilities to maintain users and roles.

@@ -1198,7 +1201,8 @@ roles) are cached within Tomcat for the duration of the user's login. (For FORM-based authentication, that means until the session times out or is invalidated; for BASIC authentication, that means until the user - closes their browser). + closes their browser). The cached user is not saved and + restored across sessions serialisations.

Administering the information in the users file is the responsibility of your application. Tomcat does not provide any built-in capabilities to maintain users and roles.

--------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org