and more in a single search tool across platforms. Read the announcement here. |
02/27/2023 11:44 PM
Revoking multiple revoke access for an end user is causing the 1st entitlement to not getting revoked from application end while other remaining remove access are getting updated.
For eg: If U1 has 5 entitlements and we trigger remove access for all these 5 entitlements then the 1st entitlement will not get removed from application end but remaining 4 entitlements will get removed from application end.
Note: All remove access task are getting complete in Saviynt with status code: 200 Success response.
[{
"RUNFOREACHENT": "true",
"REQUESTXML": "<soapenv:Envelope xmlns:soapenv=\"http://schemas.xmlsoap.org/soap/envelope/\"><soapenv:Header></soapenv:Header><soapenv:Body><mesa:INTEGRATION xmlns:mesa=\"http://www.sterlingcommerce.com/mesa\"><Operation_Flag>REMOVE_PERMISSIONS</Operation_Flag><USERNAME_AND_PERMISSION_DETAILS><USERNAME>${task.accountName}</USERNAME><PERMISSION_TO_BE_REMOVED>${entTask.entitlement_valueKey.entitlement_value}</PERMISSION_TO_BE_REMOVED></USERNAME_AND_PERMISSION_DETAILS></mesa:INTEGRATION></soapenv:Body></soapenv:Envelope>",
"RESPONSEMAPPING": {
"RESPONSECODE": "Body.processData.ProcessData.ServerResponse.ResponseStatusCode"
},
"SUCCESSCRITERIA": {
"RESPONSECODE": "200"
}
}]
Thanks
Solved! Go to Solution.
02/28/2023 12:03 AM - edited 02/28/2023 12:04 AM
Hi,
02/28/2023 12:08 AM
Hi,
1. Is Task getting created for 1st entitlement -- YES
2. No error in provisioning comments -- "RESPONSECODE": "200" is the provisioning comment.
03/22/2023 10:36 AM
"RUNFOREACHENT": "true" was the solution for it.
It was not causing the 1st entitlement not to get revoked from the application end because the API doesn't allow you to revoke access but was giving success 200 response which started all the confusion.