Defining Custom Correlation Keys

A rule cannot compare an account value on a resource with an Identity Manager value unless the value is stored in the system. The accounts[Lighthouse] attribute stores many of these values, but additional values must be added with the Extended User Attributes Configuration object. The system does not save attributes that are not registered in the configuration object.

By default, the following attributes are included as extended user attributes:

• firstname

• lastname

• fullname

The fullname extended user attribute must be added to the list of QueryableAttrNames.

If you want to use a different attribute, such as an employee ID as part of a correlation rule, then you must add it to the User Extended Attributes configuration object. Use the following steps to do this:

To Define a Custom Correlation Key

1. Access the Identity Manager debug page at http://PathToIDM/debug. The System Settings page is displayed.

2. Select Configuration from the List Objects pull-down menu. The List Objects of type: Configuration page is displayed.

3. Select the edit link for User Extended Attributes.

4. Add the new attributes to the List element, for example:

   <String>EmployeeId</String>

5. The attribute must be defined as an Identity Manager attribute on the Account Attributes (schema map) page for the resource.

6. Save your changes. Identity Manager returns to the System Settings debug page.

   The custom attribute must also be added to the QueryableAttrNames element in the UserUIConfig configuration object.

7. Select Configuration from the List Objects pull-down menu. The List Objects of type: Configuration page is displayed.

8. Select the edit link for UserUIConfig.

9. Add the new attributes to the <QueryableAttrNames><List> element, for example:

   <String>EmployeeId</String>

10. Save your changes. Identity Manager returns to the System Settings debug page.

11. Restart your application server.