How-to check why identities are not being deleted
Introduction
Sometimes you will see identities that are not being deprovisioned and you might wonder why.
Checks
The following conditions must be met for an identity to be marked for deprovisioning:
All resource allocations must have been removed
In order that the resource allocations can also be removed in the systems, the corresponding tasks must be activated
Once all resource allocations have been removed, the identity is released for deprovisioning with the current timestamp. Now, the following conditions must be true for the identity to be deleted in the target system:
A deletion delay may be configured on the associated provisioning configuration. If so, the deprovisioning release timestamp plus the deletion delay must be exceeded for the deletion process to be initiated.
Deprovisioning must be enabled on the corresponding identity type.
Deprovisioning must be enabled in the corresponding target system.
© ITSENSE AG. Alle Rechte vorbehalten. ITSENSE und CoreOne sind eingetragene Marken der ITSENSE AG.