Supported Attributes for User Data Load Filtering

When configuring an Orchestrated System to on-board data from Oracle Identity Governance, it is possible to filter the user data you want to ingest in Oracle Access Governance. You can restrict which users are on-boarded by setting filters on identity attributes such as department, employee type, location, and others.

User Data Load Filtering Characteristics

You should be aware of the following characteristics of user data load filtering befire configuring filters in your Orchestrated System.

• Matching of user search filters and user data values filtering is case sensitive. For example. a filter of department = Human Resources would not return users with a value of department = HUMAN RESOURCES, or Department = Human Resources.
• If no users or accounts match the user data load filter, then no data will be ingested from Oracle Identity Governance by Oracle Access Governance. In this case, however, the data load itself will be labelled as successful in the activity log, even though no identities or accounts are on-boarded.
• User data load filter values cannot exceed 1000 for any given filter attribute.
• If an agent is already installed, an agent upgrade is required to enable user data load filters. See Agent Example Usage for details on how to upgrade your agent.

List of Supported Attributes for User Data Load Filtering

You can filter users ingested from Oracle Identity Governance based on the following attributes.

Table 1-2 List of Supported Attributes for User Data Load Filtering

Oracle Access Governance Attribute Name	Oracle Identity Governance Attribute Name
employeeType	usr_emp_type
jobCode	usr_job_code
department	usr_dept_no
location	usr_location
state	usr_state
postalCode	usr_postal_code
country	usr_country
managerUid	usr_manager_key
managerLogin	usr_login (usr_login of manager)
organizationUid	act_key
organizationName	act_name act_name of act table
territory	usr_territory

Example User Data Load Filters

Some examples of usecases you can configure using the User Data Load Filter functionality are provided below:

Table 1-3 Example User Data Load Filters

Usecase	Configuration Parameters
User with department=Product Development and jobCode=IC004 or M0003	userFilter1Name=department userFilter1Value=Product Development userFilter2Name=jobCode userFilter2Value=IC004~M0003 userFilter3Name= userFilter3Value= filterValueDelimiter=~
User with state =Kent and organizationUid=1 or 4	userFilter1Name=state userFilter1Value=Kent userFilter2Name=organizationUid userFilter2Value=1~4 userFilter3Name= userFilter3Value= filterValueDelimiter=~
User with postalCode = 78045 or 12204 with custom delimiter ##	userFilter1Name=postalCode userFilter1Value=78045##12204 userFilter2Name= userFilter2Value= userFilter3Name= userFilter3Value= filterValueDelimiter=##
User with managerUid = 17981 or 17854 and managerLogin = DINORAH.PREWITT or JOELLA.SHANNON	userFilter1Name=managerUid userFilter1Value=17981~17854 userFilter2Name=managerLogin userFilter2Value=DINORAH.PREWITT~SHIRLEY.THOMAS userFilter3Name= userFilter3Value= filterValueDelimiter=~

Note:

Filter value name and the value of the filter are both case sensitive. Using the example above, any of the following would be an invalid filter, and return no results:

• Example 1:
  • userFilter1Name=MANAGERUID
  • userFilter1Value=17981~17854
  • userFilter2Name=managerLogin
  • userFilter2Value=DINORAH.PREWITT~SHIRLEY.THOMAS
• Example 2:
  • userFilter1Name=managerUid
  • userFilter1Value=17981~17854
  • userFilter2Name=managerLogin
  • userFilter2Value=Dinorah.Prewitt~SHIRLEY.THOMAS
  • Example 3:
    • USERFilter1Name=managerUid
    • userFilter1Value=17981~17854
    • userFilter2Name=managerLogin
    • userFilter2Value=DINORAH.PREWITT~SHIRLEY.THOMAS
• Example 4:
  • userFilter1Name=managerUid
  • userFilter1Value=17981~17854
  • userFilter2Name=managerLogin
  • USERFILTER2VALUE=DINORAH.PREWITT~SHIRLEY.THOMAS