Unable to pull the entitlements with webservice connector.
Defined the entitlement type as Roles,
Added the Roles in account schema.
Configured the operation on aggregate groups-Roles.
But the aggregation is success and no date is being pulled.
Hi @nandiniks1
Have you tried the same configuration in Postman, is it giving you the results that you need?
Hi @nandiniks1 , i have couple of questions are you able to pull the role type entitlements from postman setup
Is this role entitlement type end point different with normal entitlement endpoint
In xpath config please $.attribute path
Or if you can paste sample the response of role entitlement out i will help you to setup
Thanks in advance
Avinash
Hi @nandiniks1 ,
are you able to pull roles in Postman
Hi @nandiniks1 ,
try hitting the roles endpoint directly in Postman and check the exact structure of the response.
The postman o/p is as below.
{
“data”: [
{
“id”: “xyz”,
“name”: “xyz”,
“fullyQualifiedName”: “xyz”,
“displayName”: “xyz”,
“description”: "xyz,
“updatedAt”: xyz,
“updatedBy”: “xyz”,
“href”: “https://xxx/api/v1/roles/xxx”,
“allowDelete”: false,
“deleted”: false,
“provider”: “system”
},
The same format is for user info API, the account aggregation is working as expected.
Given as below, Postman gives the o/p
The issue might be in your Response Mapping, try mapping id and name from the response to your entitlement schema, otherwise ISC doesn’t know what to pull even if the aggregation completes.
Hm, i was certain that this might be what was missing but the mapping looks correct, so the issue is something else.
Hey @nandiniks1 ,I see issue with your response mapping
Please update response mapping with following syntax
Id — >$.data[*].id
Name → $.data[*].name
Lmk if you still need help if you found fix please mark it as solution
Thanks in advance
Tool reference Json Path Evaluator | SailPoint Developer Community Json Path Evaluator | SailPoint Developer Community
Hi @nandiniks1 , Are you able to see the response in postman for the same api and with same parameters being passed?
Please check the response mapping and the unique attribute defined in the entitlement schema, whatever the field you choosed as entitlement id, it should be unique one.
Hi @nandiniks1
What is the output do you see when you run the entitlement aggregation. Do you see the entitlements processed 0 or do you see the actual number.
Can you also please also confirm if the operation type to read the roles is group aggregation - roles , as i see in your description that you have created different entitlement type roles.
Please let us know the information so we can assist further.
Thank You.
Regards
Vikas.
Hi @nandiniks1 , in the response mapping give Attribute path as $.id
@nandiniks1 , please post the response from postman, it will help us troubleshoot the issue
Hi @nandiniks1 ,
Your root path in entitlement aggregation should be $.data[*]
and in the response mapping , you have to give the attribute path as $.id
Here $ represents root path.
Hope this helps you.
Thanks
Tried with the above input, bad is it didn’t work. In the root path i gave $ and response mapping as mentioned above.
Tried with as well, my bad it didnot work .
