Identity Collection

The Identity Collector is a software component responsible for synchronizing identity data (for example, accounts and attributes) from identity stores.

Examples of Identity Collectors include Active Directory (the most common Identity Store), NIS Identity Collector (used in Linux/Unix environments), Microsoft Azure Active Directory (used for cloud applications), and a Data Source Identity Collector.

You define Identity Collectors by creating a new Identity Collector, which represents the main Active Directory Domain, (or Authentication Store).

The section below describes how to create/edit an Active Directory identity collector. The process for creating/editing an NIS, Azure, and Data Source Identity Collectors is like that for creating/editing an Active Directory identity collector, with the main difference being actual configuration.

You can also configure and edit Cloud Identity Collectors (i.e. Box, DropBox, Google Drive, etc.).

The section, Configuring the Permissions Collector, within the Administrator guide describes how to configure users, groups, and user-groups for homegrown Permissions Collection, which is like configuring a Data Source Identity Collector.

Cloud Identity Collectors

Cloud application Identity Collectors are created in the application setup process. They will be displayed and can be edited through the Identity Collector screen.

Cloud application Identity Collectors are created through the adding application setup process.

You can see the connected fields, join other data sources, and complete dynamic field mapping.

For Cloud Identity Collectors, the Permissions Collector Scheduler can be set from the Application's wizard.

You cannot set Cloud application as authentication store.