Administration Guide › Managed Endpoint Accounts › Integrating Managed Endpoints › Create an Explore and Correlate Definition

Create an Explore and Correlate Definition

To add users that exist in an endpoint, you create an explore and correlate definition for that endpoint. Any administrator with the Create Explore and Correlate Definition task can create the definition.

Follow these steps:

1. In an environment, click Endpoints, Explore and Correlate Definitions, Create Explore and Correlate Definition.
2. Click Okay to start a new definition.
3. Fill in Explore and Correlate name with any meaningful name.
4. Click Select Container/Endpoint/Explore Method to choose an endpoint and containers if they exist. For a large endpoint, a container search may take a while; you can use the search filter to narrow the search.
5. Click an explore method for the container. The explore and correlate process includes containers you select and its sub-containers. For a directory container, it includes all the containers in the sub-tree.
6. Click the Explore/Correlate Actions to perform:
   • Explore directory for managed objects—Finds objects that are stored on the endpoint and not in the provisioning directory.
   • Correlate accounts to users—Correlates the objects that were found in the explore function with users in the provisioning directory. Two choices of correlation exist.
     • Use existing users

       Use this choice for a correlation rule that matches each account with a previously created user.

       If the user is found, the account is correlated with that user. If multiple users are found, the account is correlated with the default user. If no user is found, this option creates the user (if all mandatory attributes are known) and correlates the account with that user; otherwise, it correlates the account with the default user.

     • Create users as needed

       Use this choice when correlating accounts on your primary endpoint. This option presumes that the accounts on your endpoint are named exactly the same as the users. The correlation-matching algorithm is unused with this option. Instead, each account is associated to the user with the same name. If the user does not yet exist, it is created. No accounts are associated to the default user.

   • Update user fields—If a mapping exists between the object fields and the user fields, the user fields are updated with data from the objects fields.

     Users are created with no optional attributes such as full name, address and telephone numbers. During the initial acquisition of an endpoint, use this option to set these user attributes using account attribute values. During subsequent explore and correlates, use this option to refresh the user attributes to apply changes made to the account attributes, perhaps by tools other than CA IdentityMinder.

7. Click Submit.

Now an administrator with the Execute Explore and Correlate task completes the integration of the endpoint.