Upon deactivating a user account, the account's status is transitioned from Active to Deactivated, thereby restricting the user's ability to access any assigned applications. If the account is subsequently reactivated, it may be necessary to reassign certain applications to the user, which can be accomplished through group memberships or rules. Deactivation is executed as a background process, and its completion time may vary depending on the number of impacted users. It is possible to initiate multiple deactivation requests simultaneously, and notifications will be displayed to provide updates on the progress of each request.
Once a user account has been deactivated, the following error is received on the user interface (UI) when trying to update the values associated with a deactivated Okta profile:
This operation is not allowed in user's current status.
The error below is received when trying to update the values associated with a deactivated Okta profile via API:
HTTP 403 Forbidden | errorCode : E0000038, ErrorSummary : This operation is not allowed in user's current status.
- Universal Directory
- Okta User Profile
The profile associated with the Okta user account becomes inaccessible and cannot be edited after the account is deactivated, as per the "Deactivate a user account" section in the Deactivate and delete user accounts documentation.
To modify the profile, please follow the steps below:
-
Reactivate the account first, restoring its accessibility and allowing for changes to be made.
-
Make the modifications required to the user profile. Please note that at this point, the user may have received an activation email due to how activating accounts works.
-
After the required changes have been made, the account can be deactivated.
Deactivated user accounts are inactive, and as such, any associated information or settings, including the profile, cannot be altered until the account is reactivated.
NOTE: If it is not desired for the reactivated user to receive an activation email, the steps in this document can be followed to prevent an activation email from being sent. The ?sendEmail=false parameter should be used for this purpose.
