Target Application Displays as Null in the Okta System Log
Last Updated:
Overview
The target application displays as null in the System Log during the user.session.start event because Okta associates authentication details and target application information only after the user session begins. Upgrading to Okta Identity Engine (OIE) or migrating to the IDX flow resolves this logging behavior. When searching the Admin Console System Log for eventType eq "user.session.start", Okta Classic Engine tenants display the target application as null. Okta Identity Engine (OIE) tenants display the target application clearly for most logs, but some logs omit the target application during the authentication flow. The following image displays an example of the target application appearing as null in the System Log.
This article clarifies why the Target Application is not logged in the user.session.start event, even though it is already known what application end users are accessing on the end user's screen.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- System Log
- Target Application
Cause
Okta associates the authentication details and the target application information only after the user session begins (user.session.start) during the authentication flow.
Solution
How is the null target application logging resolved?
Upgrade the tenant or migrate the authentication flow to resolve the null target application logging behavior.
- Upgrade the current Okta Classic Engine tenant to Okta Identity Engine (OIE).
- Migrate applications using the authentication flow to the IDX flow if the tenant already uses Okta Identity Engine (OIE).
