Click HERE to see how Saviynt Intelligence is transforming the industry. |
04/12/2022 12:54 PM
I'm using the default json file provided by Saviynt for Remove Access in Servicenow and am not having any luck with it. I get the following error:
Call response: {"error":{"detail":"Record doesn't exist or ACL restricts the record retrieval","message":"No Record found"},"status":"failure"}
I noticed that the add access json file sends along:
"httpParams": "{\"role\":\"${entitlementValue.entitlementID}\",\"user\":\"${account.accountID}\"}",
Is something like this needed in the json file to specify which user and group are being modified?
Solved! Go to Solution.
04/12/2022 01:50 PM - last edited on 01/10/2024 03:27 AM by Sunil
Originally posted on March 13 2020 at 13:18 UTC
Hi Adam,
It is difficult to get any conclusion from the provided information. Can you please share the debugLog and Remove Access JSON and which is being used along with the Postman Export dump file for Servicenow APIs in order to debug the issue to the below Email.
Email ID: Removed
Thanks
[This message has been edited to remove email address]
04/12/2022 01:50 PM
I am using the default remove access JSON file from https://saviynt.freshdesk.com/support/solutions/articles/43000463489-servicenow-connector
{
"call": [
{
"name": "Group",
"connection": "userAuth",
"url": "https://<domain-name>/api/now/v1/table/sys_user_grmember/${account_entitlements.uuid}",
"httpMethod": "DELETE",
"httpHeaders": {
"Authorization": "${access_token}"
},
"httpContentType": "application/json"
},
{
"name": "Roles",
"connection": "userAuth",
"url": "https://<domain-name>/api/now/v1/table/sys_user_has_role/${account_entitlements.uuid}",
"httpMethod": "DELETE",
"httpHeaders": {
"Authorization": "${access_token}"
},
"httpContentType": "application/json"
}
]
04/12/2022 01:50 PM
Please run the full account/access import again and then try to execute the Remove Access Task.
uuid values are populated as part of Import Account/Ent JSON.
04/12/2022 01:50 PM
This portion is still not working after a full import of accounts and access. Still getting the same error message as before. Users are not getting removed from groups
04/12/2022 01:50 PM
Please find attached the updated Remove Access JSON. This should eliminate the need to run imports to process remove tasks.