Saviynt unveils its cutting-edge Intelligence Suite products to revolutionize Identity Security!
Click HERE to see how Saviynt Intelligence is transforming the industry.
Saviynt Copilot Icon

REST Connector - Account Not getting Deleted in Target System

rohitkumarraj
Regular Contributor
Regular Contributor

Team,

I am working on REST Connector. We have a requirement to delete user's account after 45 days of user LWD.

To achieve the same, I have configured below JSON in RemoveAccount JSON field:

*****************************************

{
"call": [
{
"name": "call1",
"connection": "userAuth",
"url": "https://URL/api/v2/users/${account.accountID}",
"httpMethod": "DELETE",
"httpParams": "{}",
"httpHeaders": {
"Authorization": "${access_token}",
"Accept": "application/json"
},
"httpContentType": "application/json",
"successResponses": {
"statusCode": [
200,201,204
]
},
"unsuccessResponses": {
"statusCode": [
400,
401,
403,
404,
429,
500,
503
]
}
}
]
}

************************************************

But this JSON not getting trigger, no entry Of this JSON in logs. And pending task getting completed without calling this API endpoint to delete in target system.

The same URL & method working fine through POSTMAN. Just through Saviynt it's not working as expected.

Any input will be helpful!

Thanks

Rohit

 

7 REPLIES 7

rohitkumarraj
Regular Contributor
Regular Contributor

Adding extra info to this:

Connection JSON is working fine. All other JSON getting trigger and working, only RemoveAccount JSON not triggering in my case.  I don't even see a connection JSON entry in case of RemoveAccount scenario in logs.

Try removing httpParams": "{}",

Please share logs


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

Hi Rohit,

How are you creating a task for this use case ?

If you are using the option of "DeProvision Access" in the UpdateAccount Rules, then the logic under RemoveAccountJSON is triggered.

If you are using the option of "Disable User Accounts" then the logic under DisableAccountJSON is triggered.

Please validate and let us know.

 

Regards,

Avinash Chhetri

Regards,
Avinash Chhetri

Hi @avinashchhetri ,

In my case I am using actionable report to trigger 'Delete Account' task.

Does  'RemoveAccount JSON' not work for 'delete account' task type? Can you suggest me which JSON will be applicable for this task type?

Hi Rohit,

I'm not too sure of the Delete Account task but you can use the "Deprovision Account" as an action to create a Remove Account task from your analytics, that should trigget the logic in the RemoveAccount JSON.

Regards,

Avinash Chhetri

 

Regards,
Avinash Chhetri

Hi Avinash,

Thanks much! This solved the requirement! Our ultimate goal was to delete the account in the target and 'deprovision account' tasktype worked for us in this case.

Still it's unknown how to trigger 'Delete account' task and which JSON under REST connector works in this case. Keep us posted in case if you find anything on that.

Thanks

Rohit

rohitkumarraj
Regular Contributor
Regular Contributor

It didn't help. 

I tried two variation of it:

1. Removed {] from httpParams which means final one look like: httpParams": "",

2. Another variation: Completely removed httpParams": "{}" from the JSON.