Steps to add a new Attribute in a Source Integrated through OOTB WebService Connector

Identity Security Cloud (ISC) ISC Community Knowledge Base
, , , , ,
1

Problem

When a new attribute is getting added to the Authoritative Source which is integrated with SailPoint ISC using OOTB webservice connector, the attribute data is not getting populated in SailPoint ISC.

Diagnosis

During the initial configurations, we added the required attribute name and JSON path of attribute in “HTTP Operation → Account Aggregation” page of the source in SailPoint ISC. Also, made sure that the attribute with required name is added in the Account Schema configuration of the source. We performed the aggregation of some individual identities for the source and also performed Full Aggregation by Disabling the Optimization, still the users were not getting populated with required data of the newly added attribute.

Post analysis, we found that there was WebService After Create which was created and attached to the source. When we opened the rule, we found that the required new attribute has to be added in the Code of After Create Rule as well to make sure that data is propagated successfully to SailPoint ISC.

Solution

The detailed steps of adding a new attribute to your source which is integrated with SailPoint ISC using Web Service Connector (OOTB) is as follows.

  1. Create a new Attribute in Account Schema configuration page of respective source.
  2. Go to HTTP Operations of the source, then, open Account Aggregation operation of the source, go to response mapping and add the attribute name ( the name of attribute should be same as that added in the step # 1) and add the correct JSON Path of respective attribute.
  3. Open the source configuration from POSTMAN and validate the name of WebService After Create Rule.
  4. Open the WebService After Create Rule and add the newly created attribute name in the returning map
  5. Update the WebService After Create Rule in the SailPoint ISC.
  6. Perform the Aggregation by Disabling Optimization.
  7. Validate the Data and now, the attribute will be aggregated successfully from authoritative source to SailPoint ISC.

Note that change in the logic of “WebService After Create Rule” is required if you are using the same in your source.

1 Like