<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
Impact of Okta Integration Network App Updates on Existing Integrations
Okta Classic Engine
Okta Identity Engine
API Access Management
Overview

When developers update an Okta Integration Network (OIN) application, Okta automatically applies most changes to existing integrations. However, specific elements like the application name, logo, and System for Cross-domain Identity Management (SCIM) profile mappings do not update automatically for existing tenants. To apply these specific updates, the user must remove the existing integration and reinstall the application from the OIN catalog.

Applies To
  • Okta Identity Engine (OIE)
  • Okta Classic Engine
  • Okta Integration Network (OIN)
Solution

How do Okta Integration Network updates affect existing integrations?

 

After developers modify an OIN submission and Okta approves the changes, Okta updates the application in the catalog. Okta automatically pushes most of these updates to existing integrations. However, Okta does not automatically update the application name, the application logo, or the SCIM profile mappings for existing integrations. Developers must ensure that all modifications remain backward compatible so that existing integrations remain functional.

 

 

How are existing Okta OIN integrations updated with new changes?

 

Apply the updated application name, logo, or SCIM profile mappings to an existing integration by following these steps:

  1. Remove the existing integration.
  2. Reinstall the application from the OIN catalog.

 

 

Related References

Loading
Impact of Okta Integration Network App Updates on Existing Integrations