Update status attribute after Remove entitlement Web Services

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Hey guys,

When I Remove or Add Entitlements to a User, I need to change their account status. When removing, I need to deactivate. When adding, I need to activate.

This behavior works perfectly in the API. When the operation is performed by ISC, the API receives it and updates the user’s status accordingly.

However, on the ISC interface, this status change only reflects after a full account aggregation.

Is there a way to update the status immediately after the “Remove Entitlement” and “Add Entitlement” operations without running a general aggregation?

image
image1594×202 7.25 KB

We are mapping the response in both operations:

image
image1198×858 33.5 KB

2

I am fairly certain that when you add/remove entitlements, ISC will only update the entitlement information on the Account.

You could create a Workflow that would “enable” the account when Entitlements are added, and “disable” the account when Entitlements are removed.

3

Hi @lucassilvaasper ,

You can achieve this by running single account aggregation using Get Object HTTP operation. Add this operation at last.

4

Hi Lucas,
Why don’t you try creating a workflow with the provisioning completed trigger with filter for that particular source and in the next step perform an single account aggregation using the Http request as the action, I think it will work

5

Hi Theja,

I’ve created a Get-Object and pointed it to the Remove Entitlement operation via Parent Endpoint, but it still doesn’t work…

6

Hi @lucassilvaasper, Hope you have mapped the inactive attribute in response mapping in Get Object operation. Also does, single account aggregation works in Postman?

7

Yes, it’s mapped.
And in Postman, it works fine.
I also logged the response in the After Operation Rule, and it shows exactly as in Postman.