8.1 Publishing Identity Sources

Identity Governance publishes all identity sources concurrently to ensure that each unified identity receives the latest merged information. Identity sources always get published before application sources.

8.1.1 Planning for Publishing and Merging Identities

When using the Publish and merge option for your Identity Collectors, you will need to plan the following actions:

  • Specify the order in which your identity sources will be published

  • Specify the attribute(s) that will be used to match records from each source to identities in the catalog

  • Designate which identity source will be used as the preferred (authoritative) source for the attributes that will be used to match records

  • Decide if you want to allow or prevent new user creation when users from an identity source cannot be merged with an existing user from another identity source

For information about setting the merge rules, see Section 8.1.2, Setting the Merge Rules for Publication.

8.1.2 Setting the Merge Rules for Publication

Merge rules allow you to control which values will be stored when multiple identity sources provide information for the same fields. For example, if two sources provide an email address, data from the selected source will be saved as the primary value. If you do not select a identity source as the authoritative source for merging, Identity Governance uses the first collected value.

IMPORTANT:When collecting identities using the publish and merge setting, matching attributes are mandatory for Identity Governance to include the user when publishing. If a secondary identity source has users that do not have the matching attribute defined in the collector, they will be collected, but they will not be published.

  1. Log in to Identity Governance as a Customer or Data Administrator.

  2. Select Data Sources > Identities.

  3. Drag and drop the identity sources to their desired positions to set their priority for merging the published attributes. In general, it is desirable to place your most complete and authoritative source in position 1.

  4. To use a specific identity source as the attribute authority, complete the following steps:

    1. Under Publish and merge, expand Set merging rules.

    2. For the attribute that you want to modify, specify the identity source.

      The None (go by order) option instructs Identity Governance to use the first identity source as the attribute authority.

    NOTE:You must specify unique values for the attributes you want to match during merging. In addition, do not use an empty (null) value as a matching attribute value.

  5. Select the Save icon.

  6. Publish your pending changes.

  7. Verify the changes that you published to the catalog.

8.1.3 Publishing the Identity Sources

Since the Identity Governance catalog is comprised of the data contributed by all published sources of Identity data, you must perform a publication of Identity data only after you have performed a collection from all sources. The publication process will unify your collected data sources and populate the catalog.

If you have a scheduled collection, Identity Governance publishes the collected identities at the end of the run. You can also manually publish the identity sources.

Identity Governance uses a red diamond icon to indicate that an identity source has been collected but not published. Identity Governance shows any collection errors or warnings on the Identities and Applications data source pages.

To manually publish the identities:

  1. Log in to Identity Governance as a Customer or Data Administrator.

  2. Select Data Sources > Identities.

  3. Make sure you have collected all the identities.

  4. Select the Publish identities now icon.

  5. When you see that publication has completed, go to Catalog to view the collected information.

8.1.4 Viewing Merge Histories

Identity Governance enables you to keep track of the merge events that cause unique user IDs to be created, assigned, or changed during the publication of identities. It also tracks events where merging could not happen. The merge process might result in events such as:

  • The collected user fails to merge and does not create a new user

  • A collected user that was previously merged no longer merges and new user creation is not allowed

  • A previously merged user is split into different users, and a new user is created with a new unique user ID

  • A collected user that used to merge with one user now merges with another user, which changes its unique user ID

You can view these merge events to investigate how identities were merged and why a certain user ended up having a certain unique user ID.

To view merge histories:

  1. Log in to Identity Governance as a Customer or Data Administrator.

  2. Select Data Sources > Identities.

  3. In the upper right, select Merge Histories.

  4. Select a tab to investigate merge events.

  5. Select the Settings icon to add and delete columns.

  6. Based on your analysis and needs, change your publication options. For support with troubleshooting issues, contact your Customer Support team.