The ISC source [Web Service using Direct Connection] schema includes Owner and Requestable flags, but they aren't mapped to the actual Entitlement fields. What caused this, and how can it be resolved?

  • In the Entitlement Schema defined in the source, the attributes “Owner” and “Requestable” are present but not mapped.

  • To update the individual entitlement’s Owner and Requestable flags, you have the option to do so through the user interface or by calling the Patch API on the entitlement.

  • Is there any way or configuration available to map these values from the aggregation data?

Hi @shsakshi ,

Good day.
Please follow the below documentation for setting owner and mark them requestable.

Hi @suraj_gorle

Is it possible to update metadata during the aggregation process?

Specifically, not after aggregation through the UI, but at the time when the entitlement is aggregated to the Source, such that attributes like owner, description, and requestable are updated, similar to how the entitlement ID and entitlement name are populated.

Hi @shsakshi ,

I dont think so it is possible in ISC as of now. Anyone has better idea please share.

Hi @shsakshi Have you set up Group Aggregation as an HTTP operation? That is where you need to do the mapping. Detected Groups (ie those from an Account Aggregation) will only include the Group ID without a separate Group Aggregation.

1 Like

I agree with @j_place that you should be doing this from the Group Aggregation, not through the Account Aggregation to get the owners.

If that is not working, please describe your process for running the aggregations. Also note that if you aggregated these entitlements less than 24 hours ago, there may be some delays seeing the information, per previous comments from SailPoint.

Hi @j_place @gmilunich

I have done it through Group Aggregation only
And for the Response Mapping:

I have mapped the data attribute returned from the API to the Schema Attributes of Entitlement. But it is nothing related to Actual Entitlement Attributes

This is the schema for Entitlement in the Source: [Where only Entitlement ID and Name are mapped]

And these are attributes that the API return:

Yes, I have waited for more than 2 days, but the attributes still have not been mapped.

Hi @shsakshi Apologies, I misunderstood what you are after. I know of no OOB way to map the ISC fields Primary Owner and Requestable from the Source response during Entitlement Aggregation.

Hi @j_place
Thank you for your input; I truly appreciate it.