NoSuchFlowExecutionException

[Dan McLaughlin]

No worries.  We narrowed down the breaking change to
https://git.shibboleth.net/view/?p=java-identity-provider.git;a=commit;h=2a801e9ecc897496d9858f42f5169af270df932b

Not sure exactly what in the change is causing things to break yet.
With debug logging enabled it seems to have something to do with
webflow password login that is failing.  It never even gets to the
point that it loads the login.vm, so we know it's failing before it
gets to any of our code.  We use a custom JAAS config to do
user/password validation against a database.  We've been stepping
through it with a debugger this morning and haven't found the cause
yet, mostly because we aren't quite sure of the best place to set a
breakpoint.  All we know at this point is if we revert that one change
it works, and when we put it back things break.   Since 5.0 isn't
released I didn't want to open a ticket until we either knew exactly
where the problem was or had a fix coded up.   Knowing which change
broke things is making it a little easier to narrow down, but it was a
fairly big change.  If we find something we will open a ticket.

--

Thanks,

Dan

On Thu, Oct 20, 2022 at 12:47 AM Nate Klingenstein <ndk at sudonym.me> wrote:
>
> Ah, my apologies.  This definitely goes back on the dev list, then.
>
> On Wed, Oct 19, 2022 at 7:50 PM Dan McLaughlin via users <users at shibboleth.net> wrote:
>>
>> This is on IDP 5.0.   I've narrowed it down to something in the
>> IdentifierGenerationStrategy rework.  If I figure out what in the
>> change is breaking things, I'll open a ticket since the related ticket
>> has been resolved.
>>
>> --
>>
>> Thanks,
>>
>> Dan
>>
>> On Wed, Oct 19, 2022 at 6:23 PM Nate Klingenstein <ndk at signet.id> wrote:
>> >
>> > Dan,
>> >
>> > This is a fairly common error and a more appropriate question for the users' list.  In its most literal sense, it just means that the IdP [node] has no flow conversation in memory that corresponds to the e2s1 state presented by the client.
>> >
>> > You'll need to supply us with more details of the deployment and the usage pattern that leads to the exception.  It can be anything from bad clustering to JSESSIONID cookie mishandling and everything in between.
>> >
>> > Sorry to not have anything definitive,
>> > Nate
>> >
>> > --------
>> > Signet, Inc.
>> > The Art of Access ®
>> >
>> > https://www.signet.id
>> >
>> > -----Original message-----
>> > From: Dan McLaughlin via dev
>> > Sent: Wednesday, October 19 2022, 5:10 pm
>> > To: Shib Dev
>> > Cc: Dan McLaughlin
>> > Subject: NoSuchFlowExecutionException
>> >
>> > Any pointers on where I would look for what might be causing this exception?
>> >
>> > 2022-10-19 17:56:32,728 - 12.116.187.226 - DEBUG
>> > [org.springframework.webflow.executor.FlowExecutorImpl:160] - Resuming
>> > flow execution with key 'e2s1
>> > 2022-10-19 17:56:32,729 - 12.116.187.226 - ERROR
>> > [org.springframework.webflow.execution.repository.NoSuchFlowExecutionException:91]
>> > -
>> > org.springframework.webflow.execution.repository.NoSuchFlowExecutionException:
>> > No flow execution could be found with key 'e2s1' -- 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.
>> > at org.springframework.webflow.execution.repository.support.AbstractFlowExecutionRepository.getConversation(AbstractFlowExecutionRepository.java:172)
>> > Caused by: org.springframework.webflow.conversation.NoSuchConversationException:
>> > No conversation could be found with id '2' -- perhaps this
>> > conversation has ended?
>> > at org.springframework.webflow.conversation.impl.ConversationContainer.getConversation(ConversationContainer.java:124)
>> > 2022-10-19 17:56:32,729 - 12.116.187.226 - DEBUG
>> > [org.springframework.web.servlet.DispatcherServlet:1362] - Using
>> > resolved error view: ModelAndView [view="error";
>> > model={exception=org.springframework.webflow.execution.repository.NoSuchFlowExecutionException:
>> > No flow execution could be found with key 'e2s1' -- 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.,
>> > request=org.apache.catalina.connector.RequestFacade at 1070fdac,
>> > encoder=class net.shibboleth.shared.codec.HTMLEncoder,
>> > springContext=Root WebApplicationContext, started on Wed Oct 19
>> > 17:39:57 CDT 2022,
>> > response=net.shibboleth.shared.spring.servlet.impl.DynamicResponseHeaderFilter$ResponseProxy at 1fe54716}]
>> > 2022-10-19 17:56:32,730 - 12.116.187.226 - DEBUG
>> > [org.springframework.web.servlet.DispatcherServlet:1128] - Completed
>> > 500 INTERNAL_SERVER_ERROR
>> >
>> > --
>> >
>> > Thanks,
>> >
>> > Dan
>> > --
>> > To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net <mailto:dev-unsubscribe at shibboleth.net>
>> >
>> >
>> --
>> For Consortium Member technical support, see https://shibboleth.atlassian.net/wiki/x/ZYEpPw
>> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net