Sunset Date - EntitlementRemove Keeps Being Triggered

IdentityIQ (IIQ) IIQ Discussion and Questions
, ,
1

Which IIQ version are you inquiring about?

8.3

Please share any images or screenshots, if relevant.

1. Audit Page with events for affected identity;

image
image1020×427 17.8 KB

2. Example of EntitlementRemove event;

CensoredPic
CensoredPic969×754 69 KB

3. Identity Page - Entitlements

image

4. Entitlements Details;

image
image458×172 3.28 KB

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

Currently we are trying out the SunSet date feature to implement temporary entitlements. We wanted to make sure it worked with our implementation, specifically with our logical applications.

After trying it out, it seems that it worked as the entitlement was removed from the accounts, but it lingers on the entitlement page as the IdentityEntitlement wasn’t removed.

Our current problem is the continuous EntitlementRemove requests, as can be seen in image 1. We think this is due to the lingering entitlements, and we are working on it.

We wanted to know:

  • Is there any way to limit the amount of EntitlementRemove requests?
  • What would be the best way to remove these sticky entitlements?

Thanks,

Tiago Mamouros

2

Hi @tmamouros

Please follow the steps mentioned in this article for sticky entitlements - https://developer.sailpoint.com/discuss/t/resolving-sticky-entitlements-common-causes-and-solutions/96383

3

I would suggest is to create a task and schedule it to basically remove this stick entitlements.

Let me know, if you need assistance with the task/rule

4

Thanks @naveenkumar3,

From my understanding i need to deal with both the AttributeAssignment and the IdentityEntitlement.

Can i just use the Terminator object to delete the IdentityEntitlement, or is this not the best way to handle it?

5

I think it should be okay. We are doing the same in our project as well, using Terminator object to delete the identityentitelement

1 Like