Configuring Requests for Multiple Entitlements

The connector can send a single request for several instances of one entitlement type to the managed system. For example, you can send a single request for several instances of RoleID.

Note
The connector must send multiple requests for different entitlement types. However, the each request for that entitlement type can include several instances.

To enable this feature, set the addRemoveEntInSingleReq parameter to true as follows:

You can configure the values of the following attribute using the SailPoint REST API, refer to SailPoint REST API - Update Source (Partial).

Copy 
[
  {
    "op": "replace",
    "path": "/connectorAttributes/addRemoveEntInSingleReq",
    "value": "true"
  }
]

Note
For more information on SailPoint's REST APIs, refer to Best Practices: REST API Authentication and REST API - Update Source (Partial) in the SailPoint Developer Community.

The following is a JSON string example for the payload: 

Copy 
{
  "addRoleIds": $plan.addRoleIds$
}

If addRemoveEntInSingleReq is set to false, then the placeholder value for the attribute marked as an entitlement is passed in separate API requests.

  • First request payload:

    Copy 
    jsonBody={ "addRoleIds": "9dd23398-b905-4878-b7ad-bc02d22171d9" }

  • Second request payload:

    Copy 
    jsonBody={ "addRoleIds": "8defe39c0-54f6-47b4-8a15-fcc2622923sk" }

If addRemoveEntInSingleReq is set to true, then the placeholder value for the attribute marked as an entitlement is passed as an array and is executed in a single request.

Single request payload:

Copy 
jsonBody={ "addRoleIds": ["97ee39c0-54f6-47b4-8a15-fcc262292386","8defe39c0-54f6-47b4-8a15-fcc2622923sk"] }