Okta User Reactivation Appears as an Activation Event in the System Log
Last Updated:
Overview
The Okta System Log displays different events for user activation and reactivation depending on the trigger source. A reactivation event occurs when a provisioning job or an import from an application integration triggers the action. An activation event occurs when a user transitions to an active state manually or completes profile setup.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- System Log
- User Lifecycle Management
Solution
When does a user reactivation event occur in the Okta System Log?
Okta creates a Reactivate Okta user (user.lifecycle.reactivate) event only when a provisioning job or an import from an application integration triggers the action. The actor for this event appears as the administrator who revalidated the Application Programming Interface (API) connection, the administrator who initiated the action, or the Okta System (SystemPrincipal). Okta does not trigger this event when a user in a RECOVERY (Password Reset) state successfully resets the password. Review the following image for an example of a user reactivation event in the Okta System Log.
An activation event occurs when a user transitions to an active state.
Okta creates an Activate Okta user (user.lifecycle.activate) event when a user transitions to an ACTIVE state through one of the following methods.
- An administrator manually activates a user from the Okta Admin Console. The administrator who performed the action appears as the actor.
- A user in the PROVISIONED (Pending User Action) state completes the profile setup using an activation email.
- An application integration, such as Workday, reactivates a user via a provisioning job or import. A
user.lifecycle.reactivateevent occurs first, followed immediately by auser.lifecycle.activateevent. Both events share the sameTransactionID, indicating they represent the same action. - The administrator who last revalidated the API connection typically appears as the actor for this event, but this differs based on the provisioning source.
Review the following image for an example of a user activation event in the Okta System Log.
NOTE: An import from a profile source does not change the status of a user if they are in a PROVISIONED (Pending User Action) or SUSPENDED state. An administrator must perform a manual action to change the status. For example, Okta triggers the user.lifecycle.unsuspend event only when an administrator manually unsuspends a user.
