We are in the early research stages of deploying cas at our college.
In talking with another school, one of their headaches comes from
dealing with multiple different timeout values across applications and
cas.

I'll try to summarize what the other school was telling me:

Since the cas authentication has a timeout value, and the application
has a timeout value, users become confused if, say, they started a
session in one application, used up half the cas timeout value, went
into another casified application, and then were timed out early
because the cas session from the prior application ended.

Is that a mis-configuration issue or a real issue that cas admins have
to contemplate?  If it is a real issue, what are some of the best
practices around dealing with discrepant timeout values across
multiple applications?

thank you,

Jason Whitener
Portland Community College

-- 
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

Reply via email to