If you import data sources that contain cardholders, cardholder groups, or credentials that have an equivalent in Security Center, you get duplicated entities. To avoid getting duplicates, create a Security Center data source that specifies the fields to use as global keys. Entities that share the same data in a global key field are considered to be the same entity, so they are merged during synchronization. A global key can be any field that contains unique data for each entity; for example, an employee's ID or email address.
Before you begin
- Read How associating entities works.
- From Server Admin, back up the Directory database.
- Remove any duplicate entities already in Security Center.NOTE: Only the first matching entity is merged. If there are duplicates in Security Center now, there will still be duplicates after the merge.
- Prepare your external data source and choose the fields that will be the global keys, as described in:
What you should know
- It is strongly recommended that you test a merge on a staging system first.
- If your data source has no activation or expiration dates for cardholders or
credentials, Security Center adds
activation dates during the merge. To prevent these activation dates from being
used when determining whether or not a cardholder or credential is active, you
can choose to ignore the dates for either or both of these features.
Procedure
-
In the Data sources section, click Add data
source (
).
-
From the Source list, select
Security Center, and then click
Next.
-
Give a name to this data source, set whether to ignore cardholder and
credential dates, and then click Next.
-
Click Finish.
-
On the Properties page, under
Synchronization, turn on Automatic
synchronization.
-
If a synchronization does not automatically occur, click Synchronize
now.
