Share all details about your problem, including any error messages you may have received.
Hi Developer Forum,
For a WebService application:
Scenario: Raise an access request for multiple entitlements > results in Account Creation.
API only supports a single entitlement i.e. an account can only be created with one entitlement/an account can only be added with one entitlement.
Endpoints for Create Account and Add Entitlement operation are the same.
Observations:
Since the Admin role was approved first, that item was provisioned first as part of Create Account operation and the Get Object operation updates the id returned from the API.
For the second Viewer role, the Add Entitlement operation is called second, and is provisioned to the user.
Once the Perform Identity Request Maintenance task is executed, this is how the request looks. The entitlement which was provisioned shows up as Failed in the access request. (As shown in the screenshot)
Thank you for replying Emanuele! The issue is that even though the Add Entitlement operation is called and entitlement is provisioned successfully, the status of the entitlement is Failed in the access request.
Hi @sonali_manhas, if I’m understanding correctly, the application does support a user having multiple values for an entitlement, but the api only allows adding one value at a time.
Check your application xml and see if “addRemoveEntInSingleReq” is set or not.
This was resolved by configuring the identity attribute for the account schema as an actual identity attribute (for example: email), whose value will be available, instead of an id generated from the target side.
