This content has been marked as final. Show 3 replies
Thanks for the suggestion. As it turned out, I did not have Retrofit checked but unfortunately that did not resolve the issue. The behavior remained the same after checking and re-running 'Evaluate User Policies'.
I may have a workaround for this issue that I am in the process of implementing. I'm creating a job that will run right before 'Enable User After Start Date' that will update the USR_POLICY_UPDATE field to'1' if the status of a user is 'Disabled Until Start Date.' Then the user will get enabled, assigned the appropriate roles via rules, and 'Evaluate User Policies' should run and now find this user and apply the access policies.
Anyway, seems like there should be a simpler answer so I'll keep checking here if anyone has one. I'll also update if the above workaround works.
I've seen that happen before... try one other thing to test, go ahead and perform a modify on the user who has the role, and not the resource(s). Login as xelsysadm, look the user up, edit the Description field or some other attribute, and click apply. Let me know if this then provisions the resource(s) to the user.
If this works, you can do a bulk modify of users (Advanced Search-> Select Multiple Users -> Bulk Modify button) to toggle an attribute back and forth. This should trigger the RO provisioning.