Return
-
Title
OAT (ownership allignment tool) not matching users -
Description
Running OAT with all defaults options but no matching is occurring. AD is working properly, ad_users is populated correctly, but when oat_match runs, it does not match any users even though we have verified multiple users. -
Cause
The issue is that the AD environment doesn't have UPNs set on their users and currently OAT requires them. OAT shouldn't require UPNs just to match an AD user with a local user.
-
Resolution
Defect ID #28378 has been created for this issue and has been resolved as of QAS 4.0.3.215. UPNs will still be required when doing local user mapping or user overrides. -
Change Request
28378