Hello Geeks,
We have a requirement when any user requests Access from Manage Access, If user has some identity Attribute value and Requested Access has some specific value. So it shouldn’t submit.
For this requirement, I have configured rule and when I’m requesting for single Access , It is working fine.
Issue is when I’m requesting for 2 user . 1 user has Policy Violation and another one not.
So is there any way it should stop submit untill we remove another user from the request.
Hi @sbhagat,
I am not sure at all, but you can try to modify the LCM Provisioning workflow:
try to modify the behavior where a policy violation is detected, inserting a form where you can remove the accont.
Also, you can configure the form action with Cancel → exit and Confirm → continue with the provisioning
Hi @sbhagat ,
When access is requested for multiple users, the LCM workflow executes independently for each user. This means that if you request access for two users in the same request, the LCM workflow will run twice—once for each user. If a policy violation occurs for one user, a work item is created in the backend, but it won’t be visible in the UI.
I’m not certain if there’s a way to control this behavior.
I think a conditional step in the LCM provisioning workflow should do the trick. Could you describe the issue you are facing when requesting more than one user?
