Disconnected Entitlements not on the account after cleaning sticky

Which IIQ version are you inquiring about?

8.4P1

Please share any images or screenshots, if relevant.

[Please insert images here, otherwise delete this section]

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

[Please insert files here, otherwise delete this section]

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

We are having disconnected entitlements showing under entitlements tab and not under the account.

We already have a sticky entitlements cleanup rule scheduled from sailpoint but these are only existing in the entitlements table as disconnected, source as LCM/Batch etc.. and assigned as 1 or 0

Some of these entitlements are part of access request and filtered from the past.

Tried aggregation, refresh with max options but not cleaning. We have around 40k records like this in identity entitlements table. Example below.

Below is the sticky entitlements rule that we are using.

StickyEntitlementsCleanup_Rule.xml (3.4 KB)

image

@sha02031

Can you please explain your usecase, problem and what you want to achieve.

This will help us to guide you to resolve your problem.

@sha02031

  1. Cancel Open Requests: Check for pending access requests for each entitlement; if found, cancel them and verify if the entries clear.
  2. Check for Duplicate Accounts: If the issue persists, verify if the user holds the same entitlement under a different account name.
  3. Manual Cleanup: If a duplicate account exists, you may manually delete the stuck entries.

Regards,

Sivaprakash.

@sha02031 We had a similar issue and we introduce a rule runner task to fetch such entries from IdentityEntitlements and delete it from system. You can have them schedule to run weekly or as per your convenience.

Note: Found a fix?Help the community by marking the comment as solution. Feel free to react(:heart:,:+1:, etc.)with an emoji to show your appreciation or message me directly if your problem requires a deeper dive.