Deleting incomplete SEIC User records provisioned in error

[Ian]

Hi folks, the support engineers suggested we raise this in the forum for suggestions.

We have an issue with User records that were provisioned in error (via a single-attribute csv update upload not matching on the Username).

These records are very incomplete, and affect our provisioning of genuine users.

As they are in the 'number range' of usernames our source database issues, so actual users don't get provisioned when the number is later allocated, as they later count as an update to one of these blank records, rather than a brand new users record (so on Create doesn't trigger). There are thousands of these blank users, so I'd also like to remove them for that reason too.

What I think we want to do is to delete these 'blank' user records from SEIC (with help from Saviynt Ops)- but we're not sure if there are other considerations to doing so, or if it is likely to cause problems.

Many thanks in advance for any input.

[rushikeshvartak]

As per GDPR, none of records can be deleted, 

For above use case you can do below steps

• Update username /systemusername
• Update respective user properties
• Make user inactive

Above can be done manually/file import /using API

[Ian]

Thanks for the reply Vartak.

I am not certain how the GDPR would apply, firstly as we're an educational institution in New Zealand, and secondly none of the records we're looking at deleting are for actual people, which is where our domestic laws would come in. They are blank, junk records in the users table. They have no personally identifiable information on at all, and at the moment of deletion the username would not be linked to any individual either.

It's more accurate to describe them as junk non-identity linked records in the users table, than actual User records.

I had also considered some of the other options.

Inactivating the User would still leave them present in the users table, so when the username is later allocated, they'd still not receive On (User) Create processing at that time.

Updating the username to be out of the allocation range should technically fix the problem, but is a less desirable solution than deletion, as we'd still be left with thousands of junk records in the users table.

Can you expand more on what you mean by 'update respective user properties'?

Many thanks again.

[rushikeshvartak]

After the users are created in EIC, you cannot delete them. However, you can make them inactive.

We should never ever be deleting users in production. What you can do out of the box is that scrambling the IDs and they can be kept inactive and will not show up anywhere in the system.(Considering audit concern)

https://saviynt.freshdesk.com/support/solutions/articles/43000571856

refer similar post https://forums.saviynt.com/t5/identity-governance/why-there-is-no-feature-to-delete-users-from-tenan...