You are viewing an earlier version of the admin guide. For the latest version, please visit EmpowerID Admin Guide v7.211.0.0.
Automated Account Cleanup
As an administrator, you can leverage EmpowerID to automate the process of deactivating and retiring stale user accounts based on your organization’s security policies. Rather than relying on time-consuming and potentially risky manual methods or scripts to mark accounts as inactive, disabling and deleting them based on policy, you can configure a few simple settings in EmpowerID. Not only does this remove the burden and risks associated with other methods, it provides a safety net to mitigate against accidental deletion of any user account by first marking the accounts for deactivation and notifying the managers of those users, as well as other administrators, that the accounts have been identified for cleanup. The managers and administrators must give approval before EmpowerID does anything further with them. If approved, EmpowerID moves those accounts into a designated OU within your directory (for account stores with OUs, like Active Directory), where they remain until their deletion undergoes a multi-step approval process. Accounts not approved for deletion are moved back to their originating OU. Additionally, EmpowerID provides “mock run” capabilities that allow you to generate reports of what would occur in your environment using this feature.
The process involves a number of account store and resource system settings, EmpowerID system settings, workflows, Sets and SetGroups. Each of these settings can be enabled and configured to run based on your own particular security needs. Sets and SetGroups are configured out of the box but can be customized as needed.
If the account store does not have OUs, accounts identified for cleanup are not moved to a designated OU before being disabled and ultimately deleted. All other processes remain the same.
Process Flow
The process for automating the deactivating and retiring of stale user accounts is depicted in the below image. An explanation of the process follows the image.
The steps involved in the above process flow for the three workflows used in the cleanup process is as follows:
Submit Account Terminations workflow
This workflow claims account stores where CleanUpEnabled is set to true and gets the following SetGroup GUIDS from Resource System Config Settings in order to process those groups:
AccountTerminationBeforeProcessingSetGroupGUID – This setting specifies the GUID of the SetGroup containing all people needing to receive notification of a pending move and disabling of a user account.
AccountTerminationNotProcessedSetGroupGUID – This setting specifies the GUID of the SetGroup containing all user accounts to be be moved and disabled.
AccountTerminationProcessedSetGroupGUID – This setting specifies the GUID of the SetGroup containing all user accounts to be terminated. The workflow processes one account store at a time.
The workflow then checks to see if the CleanUpReportModeOnly setting is set to true on the account store. If the setting is true, all the account processing steps are ignored and the account’s AccountOrganizationStatusID is set to 3 (TerminationPending). This logs everything that the workflow would do if Report Only Mode was turned off.
If CleanUpReportModeOnly is turned off, the workflow checks to see if the OU specified by the CleanUpStaleAccountOU has a valid external OrgZone (where applicable, such as Active Directory account stores). If the CleanUpStaleAccountOU setting on the account store is not valid, user accounts will not be moved to a stale out before being disabled and marked for termination.
If the number of accounts in the account store reaches the specified threshold set on the ThresholdOnAccounts Resource System Config Setting value, the SubmitAccTerminationsApproval workflow is invoked; otherwise, the accounts are moved to the OU specified by the CleanUpStaleAccountOU setting on the account store (where applicable).
If the DisabledAccountOnMove setting on the Workflow parameters is set to true, the accounts are disabled when moved.
If an account is moved, the AccountOrganizationStatusID is set to 5 (Transfer) and the TransferDate is set to current date and time on the account.
Emails are sent to manager and admin after the account is moved. EmailTemplateManagerMoveNotification and EmailTemplateAdminMoveNotification are used as templates to send emails. The AdminManagementRoleGuids workflow parameter determines which admin users should receive the email notification.
Once the emails are sent, an AssigneeNotification is inserted for that account so that it will not be claimed again to send notifications before moving accounts.
The accounts claimed earlier for termination will be processed by invoking the Terminate Account Advanced workflow.
Submit Acc Terminations Approval workflow
This workflow creates an approval task for all accounts belonging to the Management Role specified by the ApprovalApproverManagementRoleGUID parameter of the Submit Account Terminations workflow. At least one user belonging to the Management Role needs to select and approve each account to be terminated.
Once a task is created for an account store, the TaskApprovalPendingStatus Resource System Config Setting is set to true. This prevents the system from recreating the task.
If the task is approved, all accounts selected from the Task Approval Form of the workflow are disabled and moved, and the TaskApprovalPendingStatus setting is set to false.
Terminate Account Advanced workflow
This workflow claims all accounts approved for termination, moves and terminates each one, setting the AccountOrganizationStatusID = 2 (Terminated).
Once an account is terminated, the workflow checks whether the NotifyManager and the NotifyAdminManagementRole parameters are set to true.
If NotifyManager and NotifyAdminManagementRole are set to true, the workflow checks the EmailTemplateManagerDeletionNotification and the EmailTemplateAdminDeletionNotification parameters for the email template that is to be used to send emails to the managers of each terminated user, as well as all admin users belonging to the Management Role specified by the AdminManagementRoleGuids parameter.
Next Steps
Configure automated directory cleanup