ODMAD: ReACL is failing with user profile without mapping when mapping does exist in the environment (4381071)

ODMAD: ReACL is failing with user profile without mapping when mapping does exist in the environment, checking source environment, Details.

But when map.usr is exported, that user is not present in the file.

User was read without samAccountName or UPN

This is quite a rare case where user's samAccountName is not getting populated during the initial Read. So when user's matching state is being checked, please expand user's attributes in the bottom and look for samAccountName. If it's empty, it means that user will not be exported into the map.usr file.

To resolve the issue, user's account must be removed and re-read again. This can be done by:

• move user out of scope
• perform a Read workflow, making sure that environment, Settings, "reconcile on next read" is checked
• verify that user got removed from the Quest ODMAD backend database (not listed in the source environment, Details)
• move user back into the scope and run a main workflow, that contains Read and Match modules
• user should be re-read and matched to the target one
• verify that user was read with samAccountname present

Now it's possible to perform ReACL on the device.