We have created a business role with a match list and configured it role. We have added an AD entitlement to the IT role and created a provisioning policy to update the Msds-cloudextension attribute 20 with a fixed value.
Issue is
It role is not assigned to user and value is not getting updated in AD but we can see provisioning transaction in admin console that value is committed
This condition checks whether the user is already a member of the âResearchâ AD group. If the user is not in that group, the constraint fails. As a result, the IT Role is not assigned to the user, and the provisioning form that updates the msDS-cloudExtensionAttribute20 attribute is not triggered.
Even though you see a provisioning transaction marked as âcommittedâ in the Admin Console, it just means that SailPoint successfully created and queued the provisioning plan. It does not necessarily mean the change was executed in the target system. If the IT Role wasnât assigned due to the failed constraint, the provisioning steps inside that role would not be executed.
To fix this:
Remove or relax the âmemberOfâ constraint in the IT Role so that it can be assigned even if the user is not already in the AD group. This will ensure that the attribute update happens as expected.
Alternatively, if the constraint is still required, make sure the user is added to the AD group before this role is evaluated.
Test by manually assigning the it Role . For this go to Global Settings >Role Configuration>IT Roles >No manual assignment uncheck and try to request this role