Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Message-ID: <3F6ED943.6030806@cyberspaceroad.com>
Date: Mon, 22 Sep 2003 13:13:07 +0200
From: Adam Hardy <ahardy.struts@cyberspaceroad.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20030917
MIME-Version: 1.0
To: Tomcat Users List <tomcat-user@jakarta.apache.org>
Subject: single sign-on, form-based CMA, etc
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Looking through the archives I see this topic has had some heavy 
discussion in the past, but I just want to bring it up again to verify a 
few points.

To overcome the issue with tomcat 4.x where the first session amongst 
all contexts to time-out will time-out all the user's other sessions, I 
saw Shanmugan left what appears to be a fine solution, overriding 
SingleSignOn.java's invoke() method to keep all sessions up-to-date:

http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg91451.html

To overcome the issue where each context must have its own set of login 
and error pages for form-based authentication, I saw someone saying that 
they use symlinks under Linux, at least. In fact I'm also planning to 
use symlinks to share style sheets and page templates (in Tiles) across 
my projects.

Now that I'm about to launch into doing this myself, it would be great 
if anyone else doing this could give some feedback as to how well these 
solutions perform, or any other issues that arise.

Thanks!
Adam


-- 
struts 1.1 + tomcat 4.1.27 + java 1.4.2
Linux 2.4.20 RH9


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