and more in a single search tool across platforms. Read the announcement here. |
10/14/2022 07:31 AM
create task API only allows below task types, is there any API to create "Remove Account" tasks?
I tried with DELETEACCOUNT but that creates "Delete Account" tasks and does not trigger the REMOVEACCOUNTACTION json and thus nothing happens at target.
10/14/2022 07:41 AM
REMOVEACCOUNT or REMOVEACCESS
10/14/2022 07:46 AM
REMOVEACCOUNT
This type of task:
I tried from API but this error is returned:
Request:
{
"endpointname": "Active_Directory",
"username": "caccount",
"accountname": "caccount",
"assignmenttype": "ACCOUNTS",
"tasktype": "REMOVEACCOUNT"
}
Response:
"DELETEACCOUNT" tasks are not the correct type
10/14/2022 08:23 AM
Seems this is not supported
10/14/2022 08:41 AM
I'm afraid so as well, was just checking for confirmation.
Seems like oversight from Saviynt, that should also be an available capability for API.
10/14/2022 09:52 AM
Based on the API documentations, this seems like a miss.
However, are you trying to create a Remove Account Task for specific endpoint ? I'm asking because "I think" the Remove Account and Delete Account tasks use the same REMOVEACCOUNTACTION for AD and RemoveAccountJSON for REST connector paremeters respectively.
10/14/2022 10:18 AM
@yogesh I don't think this is missed from API side.
In case of remove account , task type will be 2 only difference between remove access & remove account is remove account having blank entitlement type & value hence you need to use below API to create tasks
10/14/2022 03:32 PM
or alternately you could use the /createrequest API to create a "request" but you will have to modify the workflow for such requests to be autoapproved so that it opens a task.
Here's the task after the request is approved.
10/14/2022 10:04 AM
For delete account what is task type in arstasks table
10/14/2022 08:02 PM
@rushikeshvartak 's solution works for active accounts but not for inactive accounts, I am still not able to create remove account task for Inactive Account even though it is a valid use case:
Weird why it should fail on inactive accounts, inactive accounts can be removed. API is doing a wrong validation.
@avinashchhetri 's solution doesn't work for non-requestable applications
Expected this to be much more straight forward but apparently it isn't. 😑
10/14/2022 08:25 PM
You can't create task for inactive accounts this is expected behavior.
On Request front. You can make Endpoint as Requestable but add access query such a way that it won't visible to users.
Example where usernmae='dummy'