How to treat rehirements?

Hi people. I am needing some help for thinking this scenario. I have a client who needs to deal with rehirements. As the identity is created from RH based on his person ID, ISC identity is mantained when user leaves company.

If person returns after a while, new identity will not be created, as already exists one with his ID (which conceptually is ok, because we understand that the person does not change, and identity should not).

How can I treat associated accounts (for example, AD account)? Client wants to delet accounts on leaving, and create new accounts when rehiring (for example, AD account with different samaccountname). Is possible? Is another recommended way to treat rehirements?

Yes, if during the termination process you deleted the existing accounts, you could create new accounts. With the requirement that the user gets a new samaccountname, I would create a source in ISC that has all of the used samaccountnames. When the user is rehired, I would generate a new samaccountname and store it in the historical source.

1 Like

For the historical username source, you could just set up a separate AD connection and set it to never delete records on aggregation. That way there’s no extra work to store the account names.

1 Like