This article explains what the supportuser@okta.com (SystemPrincipal) Update application SUCCESS events that Okta Admins may see in the System Logs are and what is the cause behind it.

• System Logs
• Okta Classic Engine
• Okta Identity Engine (OIE)

The Update application SUCCESS (eventType eq "application.lifecycle.update") events triggered by supportuser@okta.com (SystemPrincipal) are automatic update events, where the actor is simply the system and not an individual user. It's not a change to the tenant configuration, instead, it will be an update to an application (integrated or not integrated with the tenant).

This can be triggered by any change to the application, such as bug fixes, overall improvements, or even just a logo change. In addition, if there is a specific feature pack that was requested for the tenant, for instance, a feature that granted certain applications additional functionality, this will also be applicable. 

As feature packs grant the same ability to a subset of applications, any updates made to the feature itself will cascade as an event in System Logs similar to Update application - success with the targets being the applications supported, even if these applications may not be integrated into the environment.

The System Logs will not show what exact changes have been made, only that a change was made. If a change to an integrated application is relevant, in the sense that it modifies the existing behavior or adds new functionality, it will be included in the Release Notes, which are publicly available. Otherwise, in cases in which it's not making any meaningful difference, for instance, a Logo change or a minor performance improvement, it will likely not be included in the Release Notes as the behavior has not changed.

Related References

• System Log
• System Log filters and search