That's not an issue with CAS or the CAS client, its most likely an issue with your browser. The applications merely place objects in session. Your container manages the sessions, generally using a session-scoped cookie in your browser.
You may be closing/opening your browser fast enough that the cookie is still in memory, or you may not be actually exiting the browser completely (and just say opening a new window). Cheers, Scott On Wed, May 13, 2009 at 2:24 AM, pravi <[email protected]> wrote: > I am having the following behavior after i implemented cas server and cas > client. I am using the cas server 3.3.1 on oc4j 10.1.3.4 > > when i open the browser and login into application1 it gets redirected to > cas for authentication, After the authentication it gets redirected to > application2(This is the expected behavior and its working fine) > > At the same time if i close the browser and open a new browser the old > session will still be maintained. If i try to access application1 it will > not redirect to CAS for authentication. so the application session is still > maintained and its not redirecting to CAS for the authentication. > Could you please throw some light on this issue. > > > > -- > 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
