Unable to recreate a deleted user

[Murali_Shanmu]

Hi,

I am working on 7.2 SP6.

I used a job to delete users by setting MX_INACTIVE = TRUE. I am not able to see users from the UI. However, when I try to create this user again from the UI. it says the entry exists. If I try to run the job by setting MX_INACTIVE = FALSE ( As per config doc), this should delete the user completely. I am still able to see the User in the UI with "Inactive" status.

Any idea, how I get over this issue.

Thanks

Murali

[terovirta · Accepted solution]

Booleans in IdM work so that attribute with value "1" means logical TRUE and entry not having the attribute means logical FALSE.

So in order to activate try to remove the MX_INACTIVE-attribute.

[Murali_Shanmu · Accepted solution]

Thanks Tero. I am not very clear with this, but I will working with this attribute. I tried to recreate the user from the UI and it said the "Entry already exists". I am away for 2 weeks and will respond to you once I am back.

Thanks

Murali

[Former Member · Accepted solution]

You can't recreate a user if they exist, regardless of their status as inactive (the MSKEYVALUE exists i in the database).

You have to reactivate the user if you want to reuse them - you do this by setting MX_INACTIVE {D} to delete the current value.

Peter

[Former Member]

Hi Murali,

Hope you had a good break. First thing is setting an identity as MX_INACTIVE does not delete them, but merely hides them from normal jobs and the UI.

If you want to see them again in the UI add MX_INACTIVE to your MX_PERSON search task and then used the advanced search to find them. To edit them, you would also need a UI task configured to display inactive identities. If you add the MX_INACTIVE attribute to this UI task, you can clear the check box and make the identity active again.

To clear MX_INACTIVE from a job, the guys are right, using {D} is the way to do it.

Hope that helps,

Ian

[Murali_Shanmu]

Thanks guys. Its clear now.

When I read the below statement in the config document, I just assumed when I set Inactive to false, it would also delete the user. Because, setting a user to inactive in IdM, does delete the user in the backend systems.

By default, the web-enabled task Inactivate Identity is configured to only deactivate a user in the identity store and not delete it. In this way, the history of the user can be retained. If you want to actually delete the identity, adjust the pass accordingly. (Set MX_INACTIVE to FALSE in the Destination tab for the Inactivate Identity pass.)

Cheers

Murali