We have an scenario where people that leave company, passes to some inactive LCS, configured as “inactive-long term”. There may be cases where people come back to company after some time, and client wants to reuse this identity. In this case, identity goes back to active LCS, which is configured to enable all sources. But all accounts remains disabled. Only a manual enabling works after identity is active.
Anyone can confirm if this is due to identity in inactive-long term LCS does not process events? Which should be the suggested way to treat this scenario? I think in a workflow triggered by a LCS change from inactive to active, and whose actions were only the reactivation of all accounts.
Yes. Workflow as you mentioned should work but if your active state in identity profile is already configured for to change the account to enable, i wonder if its a bug.
just for testing, if you have another state like short term inactive, can you move this identity to the short term and back to active to test if that enabled the account?
This should be reported as a bug. When identities return to active LCS it should trigger enable accounts process if “Enable Accounts” list has any source.
Yes, this sounds like a bug. I could be because of identity state when if the identity state is not updated before the LCS updated, this could happen but seems like a bug indeed.
To solve this scenario, i think it structurally only by ensuring that enable is triggered when user moves to active state.
You could also try to have another identity state where instead of moving the user from long-term inactive to active state, you can move it to long-term inactive to short-term inactive and then from short-term inactive to active state. I think this can solve the issue but finally it needs to be solved permanently