Okta System Log Shows Multiple Policy Lifecycle Create Events For User Identification Policy By System@okta.com
Last Updated:
Overview
Administrators observe multiple policy.lifecycle.create events in the Okta System Log generated by the actor system@okta.com creating policies named User identification policy - <Policy_ID>. This occurs because Okta automatically generates a User Identification Policy for every App Sign-In Policy during feature rollout or policy creation. Administrators do not need to take any action, as this expected system behavior does not impact end-user authentication.
eventType eq "policy.lifecycle.create" and target.detailEntry.policyType eq "USER_IDENTIFICATION"Applies To
- Okta Identity Engine (OIE)
- System Log (
eventType eq "policy.lifecycle.create") - Authentication Policies (App Sign-In Policies)
- User Identification Policy (
PolicyType: USER_IDENTIFICATION) - Okta FastPass
Cause
This expected system behavior results from the rollout of the User Identification Policy feature in Okta Identity Engine (OIE). Previously, a single global setting controlled the display of the Sign in with Okta FastPass button on the Sign-In Widget. The User Identification Policy replaces this global toggle with granular, rule-based control per application. It enables administrators to configure whether the Sign in with Okta FastPass button displays during the user identification step based on the application, network zone, Internet Protocol (IP) address, operating system, or device platform.
To power the User identification tab within each App Sign-In Policy, Okta maintains a one-to-one relationship between each App Sign-In Policy and its corresponding User Identification Policy. When Okta enables the User Identification Policy feature on an OIE tenant, Okta runs a one-time automated background migration that iterates through every active App Sign-In Policy and creates a linked User Identification Policy. Whenever an administrator creates a new App Sign-In Policy, Okta automatically generates its paired User Identification Policy.
Solution
How does the User Identification Policy impact end-users?
Administrators do not need to take any action. When Okta creates each User Identification Policy, the default catch-all rule automatically inherits the existing global setting for the Sign in with Okta FastPass button. End-user sign-in flows and security posture remain unchanged unless an administrator explicitly adds or modifies rules. Because Okta automatically provisions a one-to-one User Identification Policy for every App Sign-In Policy, administrators cannot delete these policies independently of the parent App Sign-In Policy.
View the User Identification Policy in the Admin Console.
Navigate to the authentication policies in the Okta Admin Console, select the desired application sign-in policy, and open the user identification tab to view or add custom rules.
- In the Okta Admin Console, navigate to Security and select Authentication Policies.
- Select App sign-in and open the desired policy.
- Select the User identification tab to view the default catch-all rule or add custom rules by network zone or device platform.
NOTE: If the User identification tab is not yet visible in the Admin Console UI, the visual interface is still rolling out to the tenant while Okta pre-provisions the backend policy objects.
