Thanks guys, So I just realized I may have been on a wild goose chase. I took down 2 of my 3 CAS servers (don't tell on me, hehe) and I am still getting the time out errors.
But they aren't ST timeouts, they are TGT Expiration Policy timeouts. And these are probably just normal behavior. 2015-07-17 07:07:58,789 DEBUG [org.jasig.cas.ticket.support.TicketGrantingTicketExpirationPolicy] - Ticket is expired due to the time since last use being greater than the timeToKillInMilliseconds Sorry for the distraction. Bryan Wooten Tel: (801)585-9323 Email: [email protected]<mailto:[email protected]> [Identity & Access Management_combined centered] From: Marvin Addison [mailto:[email protected]] Sent: Friday, July 17, 2015 6:04 AM To: [email protected] Subject: Re: [cas-user] Service Ticket Timeout Policy Lately we have been seeing ST Validations failing because the ticket is expired. We are thinking of changing the timeout to either 15 or 20 seconds. The first thing that occurs to me is latency in ticket replication among all the peers in your cluster. That's sort of orthogonal to your question, but the root cause is interesting. And it's just a thought, could be any number of things. In any case I'd be interested to know the root cause if you drill into it and figure out, particularly if it turns out to be repl latency. M -- You are currently subscribed to [email protected]<mailto:[email protected]> as: [email protected]<mailto:[email protected]> To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user -- 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
