if any business role revoked as part of certification and that business role then it will getting assigned back to identity when new refresh is ruining.
Is there any way where we can make the config changes in iiq to avoid this situation.
Please help me to make the config change.
And also can we revoke 1 IT role, if multiple IT role associated with business role.
Part 1: Business Role Re-assignment After Certification Revocation
When a Business Role is revoked via certification, IIQ triggers deprovisioning of that role and its associated IT roles/entitlements. The re-assignment on subsequent Identity Refresh occurs due to one of these conditions:
Optimistic Provisioning is enabled — IIQ marks the provisioning as successful without confirming the connector actually removed it. The role remains on the identity cube. On next refresh with Provision Assignments checked, IIQ sees an active role assignment and re-provisions it.
Application was unavailable during deprovisioning — the removal failed silently or was queued but not completed, leaving the role still attached to the identity.
“Provision Assignments” checkbox is selected on the Identity Refresh task — this is the key trigger. If the role is still logically attached (due to either reason above), refresh treats it as a valid assignment and pushes it back.
Config fixes:
Option
Action
Optimistic Provisioning
Set to false on the application — IIQ will wait for connector confirmation before marking deprovisioning complete
Identity Refresh Task
Uncheck “Provision Assignments” if you don’t need refresh to drive provisioning
Certification Revocation
Ensure the revocation actually clears the role from the identity cube — check IdentityEntitlement and Links post-revocation
Retry Logic
If deprovisioning fails, ensure the provisioning transaction shows a failed/retry state, not success
Part 2: Revoking One IT Role When Multiple IT Roles Are Attached to a Business Role
you cannot selectively revoke a single IT role from within a Business Role construct via certification**. Certification operates at the Business Role level; all associated IT roles are bundled.
The approach:
Revoke the Business Role from the identity via certification or lifecycle event
Modify the Business Role definition — remove the unwanted IT role, retain the required one
Re-assign the Business Role to the identity
This gives you the correct end state without leaving orphaned IT role assignments. There is no supported out-of-the-box mechanism to cherry-pick one IT role out of a Business Role for a specific identity without role restructuring.
Do i need to change workflow to set Optimistic Provisioning false?
yes, refresh task checkbox is getting back assigned the role.
i have do the testing in QA environment when i revoke the access from the certification, it had removed that role but when i run the refresh task its assigned back.
in assignment rule, we are using match list, based on match list attribute it getting assign back in refresh.
@Rana123H Optimistic Provisioning should not impact role removal. Normally business role removes immediately. Could you please do this, capture the identity xml of a user → revoke a role → capture the identity xml again.
For your second case, you should split your business roles into manageable chunks where you can remove any role easily during certification.
If Business role is assigned by Assignment criteria/rule and if we remove it by LCM access request, it does not come back on Identity because of negative assignment. Which means Removal of role by LCM request has higher priority than assignment criteria of business role. I am not sure what happens in case of role removal due to Certifications. Let me replicate this in my IIQ environment
If the identity selector criteria match, the role will be reassigned automatically. This is expected behavior. You should not certify access for these roles. Instead, configure a “Role Composition Certification” to periodically review the role assignment criteria and adjust it if needed.
For the current scenario, if only a handful of users are affected and you need to prevent the role from being assigned, you can add a negative=true flag to the role assignment in the identity XML.
@Rana123H purpose of negative=true is to block the automatic reassignment. So, when it assign back, flag remains or it get removed? could you please share the xmls here for review.
I had tested in QA environment and revoke the business role; it was revoked and also IT role and associated entitlement also revoke.
I have captured the identity xml before and after revoke, as already discussed i can see negative=true set after the revoke on identity profile.
I revoke I ran certification maintenance and role refresh task again, now role are not getting assign back even role has assignment rule.
can someone confirm negative=true prevent the assignment again if role is revoked as part of certification?
In which cases negative=true will not work when revoke happen?