<div dir="ltr">Hello,<br><br>We are still trying to update idp 3.2.1 to 3.3.1. <br>Installing goes ok.<br>There is something wrong with authentication flow.<br><br>-----------------------<br>idp-process.log:<br>2017-05-24 09:40:52,745 - WARN [net.shibboleth.idp.authn.impl.PopulateAuthenticationContext:198] - Profile Action PopulateAuthenticationContext: No authentication flows are active for this request<br>2017-05-24 09:40:52,791 - INFO [net.shibboleth.idp.authn.impl.SelectAuthenticationFlow:294] - Profile Action SelectAuthenticationFlow: No potential flows left to choose from, authentication failed<br>-----------------------<br>idp.properties<br>idp.authn.flows= Password<br>------------------------<br>general-authn.xml<br><bean id="authn/Password" parent="shibboleth.AuthenticationFlow"<br>                p:passiveAuthenticationSupported="true"<br>                p:forcedAuthenticationSupported="true" /><br>------------------------<br>password-authn-config.xml<br><import resource="jaas-authn-config.xml" /><br>-------------------------<br><br>JAAS-authentication is a java module which uses Radius libraries.<br><br>The same configuration works with idp 3.2.1.<br><br>Could there be something with the session? We uncommented<br>idp.authn.flows.initial = Password<br>Idp asked and verified username and password. Then the same error appeared.<br><br>SP shows this error:<br>---------------------<br>opensaml::FatalProfileException<br>The system encountered an error at Wed May 24 09:27:59 2017<br>Please include the following message in any email<br>opensaml::FatalProfileException at (<a href="https://xxxxx/Shibboleth.sso/SAML2/POST">https://xxxxx/Shibboleth.sso/SAML2/POST</a>)<br>SAML response reported an IdP error.<br>Error from identity provider:<br>Status: urn:oasis:names:tc:SAML:2.0:status:Requester<br>Sub-Status: urn:oasis:names:tc:SAML:2.0:status:AuthnFailed<br> Message: An error occurred.<br>------------------------------<br><br>Should we try to install 3.3.1 from scratch?<br><br>Thanks,<br>Jukka<br></div>