Hello everyone
When the lifecycleState indicates that the user is on vacation, the user account is disabled, which is fine, but the user identity is also disabled. Is it possible to leave the identity active?
Hi
In SailPoint IdentityNow, changing the lifecycle State to “On Vacation” does not disable the identity by default. If an identity is being disabled, it’s likely due to custom lifecycle rules, identity refresh rules, or account status mappings. You can stop this behavior by reviewing and modifying these configurations so that only accounts are disabled, not the identity itself.
Hi,
When you configure the Identity Profile, there’s a provisioning tab, that indicates the configuration for each lifecycle. To not disable the identity, you can leave the “Identity State” option as active, and set the accounts to disable.
Configuring this way, the identity will not turn in “inactive_short_term” or “inactive_long_term”, staying “active” on “Identity State”, but the lifecycle will change to vacation and disable all accounts.
An addiotion, if you change the “Identity State” to “inative_short_term” or “inative_long_term”, the automatic Attribute Sync will stop, then the attributes will not update on accounts, and the identity will not appear on request center, on the other hand the “Identity State” stays on “active”, the attribute sync still working and the identity will appear on request center
Exactly, this will let identity still active, attribute sync still working, identity still appearing on Request Center, and you can handle the accounts of identity whose join in the lifecycle, configuring to disable or enables all accounts, or say which account will disable or enable