and more in a single search tool across platforms. Read the announcement here. |
08/28/2023 12:27 AM
Hi Team
Automatedly provisioned AD accounts self-deleting post-provisioning, please help and suggest.
Regards
08/28/2023 01:37 AM
Hi @asharma
Can you check which system is doing the de provisioning? (IGA or Target AD)
In case of IGA, are there tasks for deletion created? Can you check the source of those tasks.
Please elaborate the issue a bit more.
08/28/2023 01:46 AM
Provisioning is done by IGA only however Disable task is not created for those accounts.
08/28/2023 02:11 AM
Then, it's better to check with the Target application team if there are controls active on the OU that are triggering this action on the target.
If there are no disable/remove account tasks in pending or completed state for those accounts, then IGA won't be the cause of deletion of those accounts.
08/28/2023 04:28 AM
I was looking at the createaccountJSON and found that we are passing customproperty30::userAccountControl#String, whereas we are not defining anything about useraccesscontrol accept enable and disable account JSON.
Are we missing or are we passing useraccesscontrol value correctly in createaccountjson
08/28/2023 04:33 AM
above one is for account attribute not for create accountjson, apologies for the confusion.