How do we trigger a workflow to continue after a request has been verified?
We have a workflow that disables AD accounts and moves them to a disabled users OU, however because we collect distinguished name as the account name in RSA, when the account moves OUs it becomes a new object in RSA, so the disable request never verifies. We want the workflow to wait for a request to be verified before continuing the workflow to move it to a new OU. Where in the workflow should we put the wait for verification node and the provisioning node to move the account to a new OU?
Is there a reason as to why you cannot use the sAMAccountName as account name instead and have the DN value as a collected attribute on the account object? That way the account can change containers and IGL will not break. I have similar logic and build some update logic that updates my DN (attribute) after a move of container. That way IGL won't break when it tries to provision anything on the account if it has changed (before the collector has updated the DN attribute of the account).