Source account not Disabled in Prehire LCS

HI All,

We have configured to Disable AD, and Entra account in Prehire LCS and Enable SNOW account. When user moved to Prehire LCS, SailPoint disables AD and Entra account but it did not Enable SNOW account.

Any inputs on this behavior?

Thanks.

You cannot do both, either enable or disable in your LCS.

Can you get us the config screenshot masking confidential info.

This is how we have configured LCS to do both Enable and Disable operations and it is working as well (in sandbox but not in Prod) but when we move user to different LCS and move back to Prehire LCS (this is also different issue because LCS should disable or enable accounts in specified LCS)

fair enough,

Whenever user moves to different LCS, it should trigger the respective operations.

So the question is, is not triggered or triggered but failed (check in events)

In the Production, we have seen SNOW account enable was not even triggered (only AD, Entra account disabled triggered) and user also moved to Prehire LCS from Different LCS.

Hmm strange, by any chance you have ServiceNow Access Profile in Access Profiles to Grant in your Pre-Hire LCS.

It is there always, but never used/thought about using both enable and disable accounts, never got this requirement as well, anyway thanks for posting this, a little learning :slight_smile:

We have ServiceNow Access Profile that we use in Role and assign the role to Users in Prehire LCS but not used it in LCS to Grant AP. Also this issue is for Existing account in Prehire LCS for new users we have Create account mapping to create disable account.

It is there always, but never used/thought about using both enable and disable accounts, never got this requirement as well, anyway thanks for posting this, a little learning :slight_smile:

Yes, I was also not aware about this until Requirement came and also saw option to Disable and Enable accounts in same LCS in new UI which was there earlier but again SailPoint reverted back to old UI.

Is the ServiceNow account for the user is in disabled state in “ABC” Lifecycle State before its being moved to Prehire? Hope it will be, just thought of asking :slightly_smiling_face:

Yes, it was disabled and SailPoint should have been enabled it after moving to Prehire.