Entitlement group not getting provisioned via Access Request

Hi All,

We have set up an access profile which contains 2 entitlements. Entitlement 1 is for assigning license to user and Entitlement 2 is for adding the user to a group. When we checked in the Application setup, we verified that the number of entitlements for that access profile is equal to 2 as seen below:
image

Access Profile:

However, when we request that access profile in the request center, only Entitlement 1 gets provisioned and the user was not added to the group. Has anyone experienced this? If so, how were you able to resolve it?

Thank you!

Hi @jasmedina,

Could you please provide more details, like any errors you see for that identity?
Go to that identity cube and check the events tab.
Other option, do you have Access History in your tenant. If yes, check if the entitlements were added or removed.
Please share screenshots of the errors, with that we can assist you easily.
Hope this helps!

Hi @Sachin_Rajathadri!

I checked the events tab and there was no error.

In the Access History, only Entitlement 1 is added and the application is provisioned.

Try adding directly app and group in target directly and see if that is allowed ?

Hi @jasmedina,

Like @vishal_kejriwal1 suggested try adding that group directly.
Also, I don’t know if this matters, but could you please check your entitlement list and see if it is marked requestable - true? if not, could you try changing that to true and test again?


hope this helps!

Which connector is this ?

2 Entitlements pointing to single attribute or different attribute ?

If it is same attribute, it should be multi-valued.

1 Like

Hi @Sachin_Rajathadri and @vishal_kejriwal1! I was able to directly add the user in the group via SCIM in postman. Entitlement is already marked as requestable.

We are using SCIM 2.0. The entitlements are pointing to two different attributes.