Upgrade your apps to Okta Identity Engine
After you upgrade your org using app branding migration, your existing apps stay on Classic Engine. Upgrade them to Identity Engine one at a time so you can catch problems early, and roll any app back to Classic Engine if you run into issues.
About this task
When you upgrade an app from Classic Engine to Identity Engine, the app comes under your Identity Engine authentication policies and user profile policies.
An app on the Classic Engine pipeline keeps evaluating its Classic Engine app sign-on policy. When you upgrade the app to Identity Engine, Okta copies that policy into a new Identity Engine app sign-in policy and maps the app to it, so the app ends up with a policy for each pipeline.
You can also set an app's authentication pipeline using the Apps API, which is useful if you're migrating apps in bulk.
Before you begin
- You've upgraded your org to Identity Engine with app branding migration. See Upgrade your org using app branding migration.
Procedure
- In the Admin Console, go to , and select the app you want to switch.
- On the Sign On tab, in the User authentication section, select Edit.
- Set Authentication pipeline to Okta Identity Engine, then select Save.
- Review the app's new app sign-in policy assignment, and configure its app sign-in policy and user profile policy settings. See Assign migrated apps to Identity Engine policies.
- Review the app's authenticator settings. See Configure the password authenticator after app branding migration.
- Repeat these steps for each app you want to migrate.
What to do next
If an app doesn't work as expected, repeat these steps and set Authentication pipeline back to Okta Classic Engine to roll it back.