Case-Insensitive User Matching Enhancement for Synchronized and Imported Data Sources

In Advanced Access Controls, a global user is created based on criteria such as username or first and last name. Each global-user ID identifies an individual user who may have varying IDs for application accounts, particularly across data sources. Since the case of a user's name (uppercase or lowercase) typically doesn't affect identification, the matching process has been updated to be case insensitive –– meaning case is now ignored during the matching process. This is true only when synchronized or imported data sources are involved. Otherwise, case is still considered.

For example:

If a user exists in Fusion security console as casey.brown and in EPM as Casey.Brown these user accounts will now be identified as the same global user.

Business Benefit

When case is ignored, user matching is more likely to accurately identify global users, which is especially important for separation of duties controls.

Steps to Enable

You don't need to do anything to enable this feature.