We are in the process of upgrading to the Utah release from San Diego. All of our instances use Okta as the Identity Provider in the Multi Provider-SSO application. When an unauthenticated user accesses our portal in a San Diego instance and they select a form that is not available to the public they are re-directed to the Okta login screen. When the same action occurs in an instance that has been upgraded to Utah, the unauthenticated user is sent to an OOB login screen.
Note, in the San Diego instance, the OOB login screen sometime flashes for less than a second before the Okta login screen renders.
How can I get the Utah instance to behave the same way the San Diego instance behaves?
