<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

Differentiate Okta Integration Network Application Creation From Updates

Okta Classic Engine
Okta Identity Engine
Okta Integration Network

Overview

Adding a pre-built integration from the Okta Integration Network (OIN) generates an application.lifecycle.update event instead of an application.lifecycle.create event in the System Log. Administrators can differentiate a new OIN application installation from a configuration change by filtering the request uniform resource identifier (URI) nested within the log event debug context. Security teams struggle to audit application lifecycle actions because the resulting event type is identical to standard application modification events.

Applies To

  • Okta Identity Engine (OIE)
  • Okta Classic Engine
  • System Log
  • Okta Integration Network (OIN)
  • Application Lifecycle Management

Solution

How is an Okta Integration Network application creation differentiated from an update?

During initial instantiation, the HTTP POST request targets a new instance endpoint. Navigate to the System Log and execute a specific search query to isolate the request URI nested within the log event debug context.

  1. Navigate to the System Log.
  2. Enter the following search query in the search bar:
    eventType eq "application.lifecycle.update" and debugContext.debugData.url co "/instance/_new_"

Loading
Differentiate Okta Integration Network Application Creation From Updates | Okta Support