A little embarrassed to admit it, but 3.2.1.1. CAS is one of those things that "just works" so our motivation to do upgrades is somewhat low.
On Fri, Sep 11, 2009 at 10:21 AM, Scott Battaglia <[email protected] > wrote: > Pat, > > Which version of CAS are you running? We usually have a thing in place to > catch that exception and reload the page correctly. > > Cheers, > Scott > > > On Fri, Sep 11, 2009 at 1:02 PM, Patrick Berry <[email protected]> wrote: > >> So, for some reason after close to 5 years of running CAS we're starting >> to run into people hitting HTTP Status 500 exception errors because the >> hidden LoginTicket on the login form expired. Yes, the mind boggles... >> But, I'm looking for the "best" (yes, I understand this is relative to >> what we need to do and our limited technical abilities to futz with the >> inner workings of CAS) solution and I wanted to run them through this >> particularly savvy community to make sure I'm not missing something obvious >> (read: easier than what I'm already thinking) >> >> 1. Add a meta-refresh to the view that would keep the service parameter. >> 2. Extend the LoginTicket expiration (oh yeah, and where exactly would I >> do that?) >> 3. Configure an error page (CAS is the only app running in this tomcat, so >> should I do it at the Tomcat level?) >> >> Thanks, >> Pat >> >> -- >> 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-dev >> >> > -- > 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-dev > > -- 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-dev
