Connection and Filters

During data import in the Org Hierarchy UI, a Base DN input is required. However, the Base DN can contain a large number of Organizational Units(OUs) with varying data, along with Users (which may include active sync devices, computers, virtual machines, and disabled users, among others).

It doesn’t make sense to import all this data directly without any filtering for Active Users; otherwise, the Org Hierarchy service will have to do the hard work to filter out all these users during the Data Import process to get the users with the license usage only.

Note: In case the Hook is selected, the Hook service also needs to transform all this unwanted data, resulting in unnecessary resource consumption and adding delays in data import.

So, providing the right Active Users filter at the time of data import is very crucial to keep the Data Import process minimal and quick.

In any organisation, all the Active users will have common attributes to differentiate them from other entities like Active Sync devices, computers, virtual machines, and disabled users etc. As an Administrator, one can log in to the AD server to understand what the best attribute combination is to identify the Active Users. Inspecting a few of the Active users' data will help in understanding.

For example, objectClass and userAccountControl attributes are the best combination to filter out the Active Users on one of our internal AD servers.

So the correct filter for one of our internal AD servers’ Data Import is (&(objectClass=user)(userAccountControl=512)).

But, this can be different for a different organisation, so as an Administrator, creating the right filter is an important step in the Data Import process. Refer to LDAP Search Filter cheatsheet to create your filters.

Once the filter is finalized, configure it in the Org Hierarchy service configuration file (<IPLA_Installation_Location>/home/config/org_hierarchy_services/config.yaml), as shown below.



Restart the InsightPro for License Analytics to make the changes effective using the command: inpro-lic set service --start.

Now, any new Data Import will make use of this filter.