Web service connector add entitlement throwing Update Account error

[shijingg (Shi Jing Wong)]

Which IIQ version are you inquiring about?

IIQ 8.4

Please share any images or screenshots, if relevant.

Please share any other relevant files that may be required (for example, logs).

Share all details about your problem, including any error messages you may have received.

Hi all, I am trying to add a group to a user account using the add entitlement operation. However, upon performing the add entitlement process, it will throw the error as shown above. I do not have a use case for update account how should I configure that?

[zeel_sinojia]

Hey,

Whenever you are provisioning attributes, which operation i.e, Add Entitlement or Update Account - gets called depend on the type of schema attribute.

In the access request that you shared screenshot for, check what all attributes are included in the plan.

Anything that is not marked as entitlement will call Update Account instead of Add Entitlement.

[shijingg (Shi Jing Wong)]

Understand you point but I have configured groupName as entitlement now I am unsure how should I put each groupName into the api endpoint? If I were to raise request for 3 entitlements it should call the endpoint dynamically thrice.

Context url

/iam/namespace/<<groupName1>>
/iam/namespace/<<groupName2>>
/iam/namespace/<<groupName3>>

Body

{
"emails": ["[email protected]"]
}

[zeel_sinojia]

The way you are referencing the groupName value is not correct. Instead you could reference that like:
$plan.groupName$

So, your context URL should look like:

/iam/namespace/$plan.groupName$

If I were to raise request for 3 entitlements it should call the endpoint dynamically thrice.

That’s true, a request for 3 entitlements would call the API thrice.

There is a configuration parameter available for Web Service application, where instead of 3 requests(or any number of requests) it will only make one single call - addRemoveEntInSingleReq .

Looking at your configuration, I think for 3 entitlements you HAVE to call 3 different URLs (each with groupName included in the contextUrl). In that case, addRemoveEntInSingleReq might not be the thing you are looking.

[shijingg (Shi Jing Wong)]

Hi @zeel_sinojia does $plan.groupName$ refer to the groupName defined in the schema?

[zeel_sinojia]

Correct.

If you check your ProvisioningPlan, you would see name of the AttributeRequest included in the plan. You could access all those AttributeRequest like:
$plan.ATTRIBUTE_REQUEST_NAME$