IT Role assignemnent

We noticed an issue where the IT role is not getting detected during the joiner event trigger.

We have a business role with a match list configured for the IT role. In the IT role, we have a role provisioning policy that updates an attribute in AD.

We have not enabled provisioning assignment in the refresh task. Instead, we added the same option in the joiner workflow.

Could you please suggest why it is not getting detect

Hi @sureshbomm

Which option you have selected in your Identity refresh task. Can you please let me know.

@sureshbomm You should keep provision assignments along with other role refresh options. If you don’t keep IIQ will not be able to assign or remove any dynamic roles.
I believe you are refreshing the identity via workflow or script in Joiner, that should be fine to add the entitlements but it’ll not remove the underlying entitlements in case of auto removals.

Hello Suresh. I would separate role assignment, role detection, and provisioning here.

For the Business Role Match List to run, Identity Refresh needs Refresh assigned, detected roles and promote additional entitlements. Provision assignments is separate and provisions the resulting access to the target applications.

As a quick test, run a scoped Identity Refresh for one affected identity with both options enabled and confirm whether the Business Role gets assigned.

Also, if the IT Role is a required role under the Business Role, you would not necessarily expect it to appear as detected just because the Business Role was assigned. Detection works from entitlements already held by the identity.

If the IT Role provisioning policy is only updating a normal AD account attribute, I would review that design. SailPoint states that Role Provisioning Policies are not intended for non-entitlement account attributes. Depending on the requirement, Attribute Synchronization or an explicit AD Modify request may be more appropriate.

You should always run role refresh with Refresh assigned, detected roles and promote additional entitlements & Provision assignments together. If you don’t keep them together, and run separately, addition of underlying entitlement will work but removal will not. You’ll end up having underlying entitlements assigned to the end users who are not satisfying the business role critieria.

Also, Role ProvisioningPolicy can be used for attribute provisioning and we have done it for multiple apps and they are working fine.

I would recommend, if you are triggering it via code or refresh, keep both the options checked.

I’m aligning with Neel on this. You should always run the role refresh with Refresh assigned, detected roles and promote additional entitlements and Provision assignments selected together.