After upgrading to oie, even when the org's policies are set to disable okta verify or when using an identity provider (idp) for authentication, users may still be prompted to set up okta verify If you have already upgraded your preview environment to oie, contact your okta account team, and a new classic tenant can be provided for testing (an additional cost might be applicable based on licensing). This is because, in oie, factor enrollment necessitates the use of 2fa.
You don’t have to remove it before you upgrade Refrain from modifying any other settings for at least one week to reduce potential conflicts. It will still function as is after the upgrade, but you should begin the migration to fastpass.
If you already own okta classic engine, there is no additional license cost to have access to the new oie feature set That being said, you’ll likely need to invest in upgrade assistance. After upgrading to okta identity engine (oie), users are not automatically logged in while they have a valid session opened before the upgrade. If okta fastpass is enabled in the upgraded org, users are prompted to enroll.
Learn how to prepare an okta classic org for upgrade to oie by identifying various types of authentication deployment models present in the okta environment. After your upgrade to identity engine, okta recommends that you validate specific features
