Quick question about LCS transitions and source configurations:
Scenario:
User transitioned from LCS A (ACTIVE/INACTIVE_SHORT_TERM) to LCS B (INACTIVE_LONG_TERM)
Sources that should be disabled in state B were added to the LCS enable/disable configuration after the user’s transition
These sources were not in the config at the time of the actual status change
Question: Will the refresh process retroactively apply the updated configuration and disable those sources for this user? Or does LCS configuration only apply at the moment of transition?
I don’t believe so, I just tested in a demo tenant and processed an identity after it was already put in an LCS that should have changed the account status, but the account status did not change. I believe SailPoint will only provision from the LCS configuration when the LCS is changed, and that configuration already has to be there.
I believe @vkashat is correct, and that SailPoint ISC will only apply the LCS Transition configuration at the time of the transition. If you make changes to the LCS, that becomes valid from that point onward.
One thing to consider is that having the account on the source in LCS B may be a valid account if it was granted after, and it was valid to have during the transition.
Agreeing with those who already posted, but here is the relevant doc:
In the Settings for Previous Accounts tab, choose whether an identity’s source accounts should be enabled, disabled, or deleted when it enters this lifecycle state
I think if it reapplied the account operations, then there would be no purpose in having the option to manually enable/disable accounts on a source or identity account list.