CAS redirects back via whatever service url is provided. If you're being
redirected back without it, then you're sending the wrong value to CAS.
Cheers,
Scott
On Thu, Feb 25, 2010 at 7:15 AM, Jamie Johnson wrote:
> Thanks for the reploy Scott. 1 question though. Looking at the
> configs it
Thanks for the reploy Scott. 1 question though. Looking at the
configs it seems like tickets by default don't expire for 2 hours, but
the CAS Session timeout is 5 minutes. If I am requesting a resource
after the CAS Timeout it fwds me to the login page which should then
see my ticket is still va
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 Johns
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
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
