Hi all, We've discovered an issue in the Jasig CAS client that is rather easy to reproduce, and presents a nasty stacktrace to the user. If you click the warning/confirmation checkbox when logging in to CAS, then go to another CASfied application and wait on the warning/confirmation page longer than 10 seconds, then click to continue, you get a 500 error stacktrace because the service ticket has timed out.
We don't want to increase the ST timeout, but there should be a better way of handling this ideally by not having the ST timeout in this scenario, or by sending the user back to a page on CAS. I've filed this as https://issues.jasig.org/browse/CASC-170 thanks, Steve -- 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
