tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ma...@apache.org
Subject cvs commit: jakarta-tomcat-catalina/webapps/docs realm-howto.xml
Date Sat, 21 Aug 2004 12:39:08 GMT
markt       2004/08/21 05:39:08

  Modified:    webapps/docs realm-howto.xml
  Log:
  Fix bug 12516. Clarify that the cached Principal is not retained across session serialisation.
   - Ported from TC4
  
  Revision  Changes    Path
  1.15      +14 -10    jakarta-tomcat-catalina/webapps/docs/realm-howto.xml
  
  Index: realm-howto.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/realm-howto.xml,v
  retrieving revision 1.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- realm-howto.xml	24 Feb 2004 12:17:22 -0000	1.14
  +++ realm-howto.xml	21 Aug 2004 12:39:08 -0000	1.15
  @@ -328,9 +328,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 <strong>not</strong> be reflected until
  -    the next time that user logs on again.</li>
  +    closes their browser).  The cached user is <strong>not</strong> saved and
  +    restored across sessions serialisations. Any changes to the database
  +    information for an already authenticated user will <strong>not</strong>
be
  +    reflected until the next time that user logs on again.</li>
   <li>Administering the information in the <em>users</em> and <em>user
roles</em>
       table is the responsibility of your own applications.  Tomcat does not
       provide any built-in capabilities to maintain users and roles.</li>
  @@ -511,9 +512,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 <strong>not</strong> be reflected until
  -    the next time that user logs on again.</li>
  +    closes their browser).  The cached user is <strong>not</strong> saved and
  +    restored across sessions serialisations. Any changes to the database
  +    information for an already authenticated user will <strong>not</strong>
be
  +    reflected until the next time that user logs on again.</li>
   <li>Administering the information in the <em>users</em> and <em>user
roles</em>
       table is the responsibility of your own applications.  Tomcat does not
       provide any built-in capabilities to maintain users and roles.</li>
  @@ -1058,9 +1060,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 <strong>not</strong> be reflected until
  -    the next time that user logs on again.</li>
  +    closes their browser).  The cached user is <strong>not</strong> saved and
  +    restored across sessions serialisations. Any changes to the directory
  +    information for an already authenticated user will <strong>not</strong>
be
  +    reflected until the next time that user logs on again.</li>
   <li>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.</li>
  @@ -1168,7 +1171,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).</li>
  +    closes their browser).  The cached user is <strong>not</strong> saved and
  +    restored across sessions serialisations.</li>
   <li>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.</li>
  
  
  

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


Mime
View raw message