Web service create and update account issues for multiple permission types

Hi All,

I’m working with a Web Services source in ISC that has two entitlement types: Groups and Profile. I’ve run into two provisioning problems and would appreciate any guidance.

## Scenario 1 – Create Account

When a new user requests both a Group and a Profile, ISC splits the provisioning into two requests:

  1. A Create request
  2. A separate Modify request

Problem: The target API requires Groups and Profile to be sent together in the same Create User call. Because they arrive as two separate requests, the Create call fails (the groups are missing), and the provisioning fails. When I add groups and profile into access profile and reaise the request it works, but I donot want do that.

## Scenario 2 – Update Account

The Update API also takes both Groups and Profile, but it overwrites the user’s existing access instead of adding it. If the existing groups and profiles are not included in the request, the API removes them and keeps only the newly requested ones.

Example:

Groups Profile
Existing access A Y
New request D Z
Expected result A, D Y, Z
Actual result D Z

To avoid the overwrite, the Update call needs to include the user’s existing Groups and Profiles along with the newly requested ones.

## Question

Is there a way to achieve both of these?

  1. Send Groups and Profile together in a single Create call.
  2. Include the existing Groups and Profiles in the Update call so current access is not removed.

Any suggestions (Before Operation rule, Before Provisioning rule, connector configuration, etc.) would be greatly appreciated.

I tried this Create operation and multiple entitlement type - SailPoint Human Fabric (SHF) / SHF Discussion and Questions - SailPoint Developer Community

Thanks in advance!

Hello KRK. I would suggest handling Create and Update separately.

1. Create Account: Set createAccountWithEntReq=true to include entitlement requests in the Create call. Use $plan.groups$ and $plan.profile$ in the payload, matching your schema attribute names.

If it is already enabled, check whether both entitlements reach the same Create provisioning plan and whether the generated JSON matches the target API. A Before Operation Rule can adjust the payload, but cannot merge separate provisioning transactions.

2. Update Account: Your target API appears to replace existing access rather than append to it.

  • If incremental APIs exist: configure the Add and Remove Entitlement operations to use them, so existing access is preserved.
  • If only full replacement is supported: use a Before Operation Rule on the operation handling the entitlement changes (typically Add and Remove Entitlement, confirm through the provisioning logs).

In the rule:

  1. Retrieve the current Groups and Profiles using restClient.executeGet(...).
  2. Merge the requested Add and Remove changes from provisioningPlan with the existing values.
  3. Read the body with requestEndPoint.getBody(), update its jsonBody entry with the merged JSON, then call requestEndPoint.setBody(body) and return requestEndPoint.

For your example, the result should be Groups [A, D] and Profiles [Y, Z].

Make sure a failed GET stops provisioning, so confirm throwProvBeforeRuleException is not set to false, otherwise the exception is logged and provisioning proceeds with an incomplete payload. Also test simultaneous entitlement changes, since separate read-merge-write calls could overwrite each other. Use conditional updates if the target supports them. addRemoveEntInSingleReq=true batches values of the same entitlement type, not different types, so it will not resolve this by itself.

If you are using the SaaS Web Services connector, use endpoint before-customization instead.