When developers update an Okta Integration Network (OIN) application, Okta automatically applies most changes to existing integrations. Specific elements like the application name, logo, and System for Cross-domain Identity Management (SCIM) profile mappings do not update automatically for existing tenants. Apply these specific updates by removing the existing integration and reinstalling the application from the OIN catalog.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Okta Integration Network (OIN)

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, logo, or SCIM profile mappings for existing integrations. Developers must ensure that all modifications remain backward-compatible so that existing integrations remain functional.

Apply new changes to existing Okta Integration Network integrations.

Remove the existing integration and reinstall the application from the OIN catalog to apply the updated application name, logo, or SCIM profile mappings to an existing integration.

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

NOTE: Updating the Authentication Method type for SCIM submissions is not supported. Submit a new OIN application instead of updating the existing one to change the SCIM Authentication type.

Related References

• How to Update an Application Integration Published to the OIN Catalog