The following documentation has been identified to review as part of the preparation needed to perform the upgrade to Okta Identity Engine (OIE). Note: additional Okta features may require reconfiguration or be disabled in order to complete the upgrade.

Okta Terraform Provider for Okta Identity Engine Upgrade
Complexity Level: Medium
Upgrade Eligibility: Eligible - Consent Required

How does this impact the upgrade to OIE?
This feature will not prevent the Okta Identity Engine upgrade; however there is significant impact to the way Okta Identity Cloud functions post-upgrade and may impact to the user experience or the general functionality. Contact your Okta Administrator to understand the potential impact listed below.

For teams using terraform to manage one or more okta tenants, there may be an impact to the current terraform provider.

How do I remediate this blocker?

Prior to the upgrade, the Terraform administrator should perform the following tasks:

• Migrate to the latest version of the Terraform Provider.

  • https://registry.terraform.io/providers/okta/okta

  • This will ensure the proper data structures will be in place for OIE.

• Note: There are breaking changes from older Terraform provider to the recent version, so must update the hcl scripts.

  • Resource name, Resource attribute name, Resource attribute values <Enums>, etc.

• These updated changes can be tested on (temp) OIE tenant (Recommended).

• When the hcl scripts are updated, associated .tfstate file also must change to be in sync with the script changes.

• Use Terraform commands to make changes to .tfstate file to keep in sync with the script changes.

Reconfiguration Impact
There would not be any impact to Terraform configuration in Okta Classic. This is just ensuring the latest provider is being used.

Post-Upgrade Impact
Post-upgrade, the terraform administrator should perform the following tasks:

• Execute a terraform plan command with -refresh=false switch to test if the script and tfstate files are in sync.

  • Must get Resources: 0 added, 0 changed, 0 destroyed.

• If any changes detected (add/change/destroy) in the refresh, make changes as necessary to the script and/or tfstate to achieve alignment with current configuration.

Is there additional training or information I can use to help me with this remediation?
No.