When enabling Polaris "NOW" Experience with MFA user experiencing loopingIssue This issue is caused by a combination of a few factors that have been noted from multiple cases. The combination usually includes: -After a clone, -then an upgrade to San Diego, -MFA configured in the instance and has enabled Unified Navigation experience on platform: glide.ui.polaris.experience = true. Expected behavior: To type in the verification code and the Now experience and instance will load within UI16 correctly. Actual behavior: This combo causes a looping to happen at the verification code page for users trying to authenticate. ReleaseSan DiegoCauseTemporary relief: Disabling glide.ui.polaris.experience by setting it to false, You will be able to login locally via MFA.Cause: There is a redirect happening that is caused by a broken image file(.iix) to become apart of the validation with the the saml authentication. Resulting in the user getting redirected to home.do to run the process again(looping). To find out what image file is causing this issue navigate to sys_properties> and search *image and see what image shows at .iix extension. This image was not set in data preservation during the clone/upgrade and therefore the image will show as a broken image generally in the upper right hand corner once you have turned off Polaris experience. Once you have identified the .iix image, you will need to navigate to that location and replace the image. To understand what is happening with the SAML redirect, the image is apart of the validation and since it is broken and no longer available its returning it as an .iix and It is using a saml redirect to get the broken image but its returning the IIX file instead of the actual image. This is due to the data asset source was not preserved for the clone/upgrade done on the instance. The image may not have been preserved causing issue with MFA with the upgrade and clone at the same time. Steps to solve for permanent fix. Upgrade should come first and then proactively check logos after patching. If the image( or any private asset source) is broken(will show as .iix with in the system properties table), please locate and replace this image and then reenable Polaris experience and see if this issue continues. NOTE:web services account login fine because it doesn't call for the image.Resolution During the clone/upgrade the logo may not have been preserved causing issue with MFA with the upgrade and clone at the same time. Upgrade should come first and then proactively check logos after patching to make sure all logos and private assets are accounted for To fix this issue please update the image: system properties> search *glide.image> see what file shows the .IIX extension and then update this image. After replacing the broken Image with a .png this will resolve the issue. reenable Polaris and test. This should result in a smooth authentication process.