Unable to login via SSO after cloning a pre-New York instance to a New York or above instanceDescriptionAfter cloning a pre-New York instance over an instance running New York or above can cause SSO logins to fail and be automatically redirected to the /external_logout_complete.do page without even being presented with the SSO login page. Release or EnvironmentNew York & aboveCauseThis can happen if the target instance was on a version New York or above and had the MultiSSOv2 version of the Multi SSO plugin and the source instance is running a pre-NY release. The IdP records on the NY instance would be using the Single Sign-on script 'MultiSSOv2_SAML2_custom' with sys_id 48d518ff73022300ec77bd49faf6a7f6. This script include was introduced in the New York release. However, since the source instance was running pre-NY version and therefore did not have this script include, the clone results in the script include not being present, thus leaving the IdP record having an orphaned reference to an invalid Script Include.ResolutionTo avoid this in the future, we recommend having at least one local login account that the admin user can use to login by going to the /login.do page The admin user can then open the IdP record and update the script include to MultiSSO_SAML2_Update1.