We are looking into trying to use CAS to synchronize all the sessions that each web application creates so that when a user is in one "CASified" webapp and then visits another, the first webapp's session is not timed out. This session is normally referred to as the Tomcat session.
Has anyone solved this problem from within CAS? -Aaron Shettleroe [Please consider the environment before printing this email] ________________________________ Confidentiality Notice:This electronic mail transmission, including any accompanying attachments, is intended solely for its authorized recipient(s). If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited. If you received this transmission in error, immediately contact the sender and delete the contents and attachments of this message. Note to recipient: This is an unsecured email service which is not intended for sending confidential or highly sensitive information. Confidential or highly sensitive information includes, but is not limited to, payment card information, social security numbers, and account numbers. ________________________________ -- You are currently subscribed to cas-user@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
