Presentation: Ungluing Sticky AttributeAssignments.pptx (1.9 MB)
Adding Refresh TaskDefinition and preRefreshRule XMLs:
Refresh Identity Cube - Remove AttAssignments.xml (2.5 KB)
icc-refresh-removeAttAssignments.xml (929 Bytes)
I would like to hear opinions on a different approach to remediating these stuck Attribute Assignments. (not preventing here, just fixing) Here’s the path I planned before reading this topic.
Because these AA’s are generating frequent repeating Provisioning Transactions which fail, I key the remediation from these failed PT objects and pull the identityName from the PT, pull the assignmentId from the Account Request. Then go to the identity and match the AA with assignmentId to determine which to terminate.
I think one additional challenge in my approach may be the need to further confirm within the PT that I have the failing AR by matching specific attributes, like the op or name. This would be possible if the PT for one identity / link included multiple entitlements for the same Application.
Thanks for your comments.