This is the same problem you have if a user is in the middle of a POST and has to redirect to CAS. You either hope it doesn't happen (not ideal :-)) or write code to store the information in a temporarily place and then replay it when they come back.
On Wed, Feb 24, 2010 at 1:42 PM, Jamie Johnson <[email protected]> wrote: > So it looks like my assumptions were correct in that if I have both > authenticating against CAS things work great. An issue arises however > when the session times out, since flex doesn't have the concept of a > page (for example trying to access http://blah.com/index.html) and > instead has the concept of views what is the most appropriate way to > handle time outs? We can't simply fwd to the CAS login page as this > will cause whatever the user was doing in flex to be lost after CAS > fwds the user back to the page. Any thoughts? > > On Tue, Feb 23, 2010 at 4:15 PM, Jamie Johnson <[email protected]> wrote: > > I have a requirement to integrate a Flex based client with a REST > > Service that is secured using CAS and was wondering what integration > > strategies others have taken. Some of the messages I've read from > > this list seem to indicate that if the Flex client is secured behind > > the same CAS instance things should work without any intervention on > > my part. Is this truly the case? Does anyone have details around > > doing this? Any information/opinions that can be provided would be > > greatly appreciated. > > > > -- > 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 > > -- 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
