We are using a webservice connector and one of the requirement is to add the user to a group. For this, I tagged the group as an entitlement and created an access profile which contains the group. The user gets provisioned to the group when I did an access request - I confirmed this when I checked the target application.
However, the change does not reflect on SailPoint side even after performing both account and entitlement aggregation. When I checked the user’s account, the entitlement does not get added and the group attribute does not get updated as well.
Hi Jasmine,
It looks like your response mapping may not be pulling the group information. Have you tried using https://jsonpathfinder.com/ to confirm the path for your group information?
Be sure that your response mapping attributes match your schema exactly as well - otherwise, the information won’t be pulled in.
If that doesn’t help, if you can share a sample response from the API and your response mapping I’m sure the community can help you troubleshoot more.
I assume you also mentioned the group membership http operation’s parent operation.
As Margo mentioned, I would also look at the response information and response mapping.
Sometimes, placing the dot(.) did the magic for me.
Ex. To get all the group ids for the user I had to use the response information as “$.Resource” and the mapping as “.id” which would technically mean the path being “$.Resource…id”
Does a user have multiple groups? In this case you need to mark the account attribute that maps to the entitlement as “multivalued”. Please check if this is the case
I agree with @NikeshRao2054 its hard to diagnose the issue without seeing more, a correctly defined schema would be the first place to check then your code.
