I believe we've explained this before on list, but in case its not easy to find in the archives, CAS3 uses Spring Web Flow which by default stores its flow in the http session.
If you have a short session and your user leaves the browser/computer for a while and comes back, the flow will have expired, triggering a new one to be created (which is why you need to enter credentials again). You can either extend your session, switch to the request based flow, or let it go. As far as I know, we never had any reports of users complaining about it. Cheers, Scott On Mon, Jun 15, 2009 at 2:46 PM, Hanh Do <[email protected]> wrote: > We're running CAS 3.3.1 and have experienced login issues whereby when > user submits CAS login form, they get back the login page with their valued > cleared-out. (A second login attempt usually is successful) .The cas logs > shows errors related to webflow: > > 09-06-13 16:14:21 [http-8137-4] DEBUG > web.NoSuchFlowExecutionExceptionResolver: Error getting flow information for > URL:/cas/login?service <http://cas/login?service>=################## > > org.springframework.webflow.execution.repository.NoSuchFlowExecutionException: > No flow execution could be found with key > '_c8D661A0D-51F5-CD26-54CB-05F893347567_k0858AD7C-4CAA-E236-2FA1-4E2842608466' > -- perhaps this executing flow has ended or expired? This could happen if > your users are relying on browser history (typically via the back button) > that references ended flows.; nested exception is > org.springframework.webflow.conversation.NoSuchConversationException: No > conversation could be found with id '8D661A0D-51F5-CD26-54CB-05F893347567' > -- perhaps this conversation has ended? > at > org.springframework.webflow.execution.repository.support.AbstractConversationFlowExecutionRepository.getConversation(AbstractConversationFlowExecutionRepository.java:229) > at > org.springframework.webflow.execution.repository.support.AbstractConversationFlowExecutionRepository.getLock(AbstractConversationFlowExecutionRepository.java:119) > at > org.springframework.webflow.executor.FlowExecutorImpl.resume(FlowExecutorImpl.java:217) > at > org.springframework.webflow.executor.support.FlowRequestHandler.handleFlowRequest(FlowRequestHandler.java:111) > at > org.springframework.webflow.executor.mvc.FlowController.handleRequestInternal(FlowController.java:165) > at > org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153) > at > org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48) > at > org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:875) > at > org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:807) > at > org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:571) > > ------ > Various JASIG postings relating to this error: > > > http://www.ja-sig.org/issues/browse/CAS-700;jsessionid=BF1AF01CE303C98C72AF277785E044CE.cas?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel > > mentioned this as a know issue and fixed in 3.3.1, however we are still > seeing it. Has someone also seen this error and know if a fix is available? > > thanks, > > Han > > > > ------------------------------ > Hotmail® has ever-growing storage! Don’t worry about storage limits. Check > it > out.<http://windowslive.com/Tutorial/Hotmail/Storage?ocid=TXT_TAGLM_WL_HM_Tutorial_Storage_062009> > > -- > 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
