On Tue, May 31, 2011 at 11:01 AM, john <[email protected]> wrote: > Wondering what the best way is to refresh their CAS session.
The CAS session is in no way related to the Web application session of the application hosting the form whose data is getting lost when the webapp session times out. Refreshing the CAS SSO session won't help you in any way deal with this problem -- it's entirely related to the webapp. > Firstly, does accessing cas.server.com/login refresh the running ticket, or > must it be cas.server.com/login?service=blah ? CAS SSO session is only refreshed when requesting a ticket, so must be ?service=x, which triggers generation of service ticket. > I can use javascript to access the page every x minutes, which is great if > they have javascript enabled. > Or I can use an iframe and meta refresh...not particularly pretty. Both those approaches amount to pinging the webapp, which is ugly but can be effective. The other option is to increase the webapp session timeout. The best solution is for webapps to develop means for persisting session data in a durable way that allows for graceful session resumption. Sadly, many apps fall into this category. M -- 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
