Issue / Bug with Unsolicited SSO after Update from IdP 3.3.1 to 3.4.3

[Martin Lunze]

Hello together,

after updating our identity providers from version 3.3.1 to 3.4.3 the 
unsolicited sso is not working anymore.

All other things work fine and after some editing no more deprecated 
warnings appear.

But I got the following errors logged:

> 2019-03-12 11:46:39,952 - ::1 - ERROR 
> [org.springframework.webflow.execution.repository.NoSuchFlowExecutionException:76] 
> -
> org.springframework.webflow.execution.repository.NoSuchFlowExecutionException: 
> No flow execution could be found with key 'e1s1' -- 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 '1' -- perhaps this 
> conversation has ended?
>         at 
> org.springframework.webflow.conversation.impl.ConversationContainer.getConversation(ConversationContainer.java:126)
>
> 2019-03-12 11:46:39,955 - ::1 - WARN 
> [net.shibboleth.ext.spring.error.ExtendedMappingExceptionResolver:136] 
> - Resolved 
> [org.springframework.webflow.execution.repository.NoSuchFlowExecutionException: 
> No flow execution could be found with key 'e1s1' -- 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.] to ModelAndView: reference to view with name 
> 'error'; model is 
> {exception=org.springframework.webflow.execution.repository.NoSuchFlowExecutionException: 
> No flow execution could be found with key 'e1s1' -- 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 45a25805, 
> encoder=class net.shibboleth.utilities.java.support.codec.HTMLEncoder, 
> springContext=Root WebApplicationContext: startup date [Tue Mar 12 
> 11:46:11 CET 2019]; root of context hierarchy}

I did not found any issue belonging to this in jira.
So my question is, did some one else also have problems with this?

My test-call looks like this:

> curl -k -L 
> https://localhost/idp/profile/SAML2/Unsolicited/SSO?providerId=https://e5.onthehub.com

Or maybe someone has a solution for me?

With nice regards.

Martin

-- 
Martin Lunze
IT-Systemadministrator

Technische Universität Dresden
Zentrum für Informationsdienste und Hochleistungsrechnen (ZIH)
Operative Prozesse und Systeme (OPS)
01062 Dresden

Tel.: +49 (351) 463-35881
E-Mail: martin.lunze at tu-dresden.de


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5742 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://shibboleth.net/pipermail/users/attachments/20190312/5908e81c/attachment.p7s>