We have had issues where someone shares a browser, logging out of a CAS service (with others services still running in tabs) for another person to use their browser. We do not have a single signoff strategy, so some of the other services still show the first person's session. So what are some approaches other institutions are doing? Second, even "shutting down" the browser does not work for Chrome. It continues to run in the background and persists cookies. While this is not caused by a bug in CAS, we still need to address this for our community. Are there best practices around this issue? Is this more an education effort?
Thanks, Benito -- Benito J. Gonzalez Manager, Enterprise Web Applications Information Technology Department University of California, Merced Desk: 209.228.2974 Cell: 209.201.5052 Email: [email protected] -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
