Resolving conflicts caused by imported entities - Security Center 5.12

Security Center Administrator Guide 5.12

Product
Security Center
Content type
Guides > Administrator guides
Version
5.12
Language
English
Last updated
2024-10-17

Conflict resolution might be necessary if you have existing user or cardholder entities in your database before importing entities from the Active Directory.

What you should know

When a synchronized entity has the same name as a local entity, the Active Directory role sees it as a potential conflict. You can use the Conflict resolution tool to view potential conflicts () and resolve them by deleting the conflicting entities in the Cardholder management task.

Procedure

  1. From the Config Tool homepage, open the System task, and click the Roles view.
  2. Select the Active Directory role (), and click Conflict resolution ().
    The Active Directory conflict resolution dialog box opens. All synchronized entities are listed to the left. The ones that conflict with a local entity are flagged in green.
  3. Resolve each cardholder conflict:
    1. Open the Cardholder management task and find the two cardholder records that are in conflict.
    2. Select one of the conflicting cardholder records and click Modify.
    3. Add any missing information that is available in the duplicate cardholder record.
    4. Save and close the cardholder record.
    5. Select the duplicate cardholder record and click Delete Cardholder.
  4. Resolve each user conflict:
    1. Open the User management task.
    2. In the entity browser, find the two user records that are in conflict.
    3. Open one of the conflicting user records.
    4. Add any missing information that is available in the duplicate user record.
    5. Click Apply.
    6. Select the duplicate user record and click Delete.
  5. Return to the Roles view in the System task.
  6. In the Active Directory conflict resolution dialog box, select the entities that are flagged as being in conflict and click Delete.
  7. Click Finish.
    This process will generate a file named Conflict_Manifest.data that documents resolved conflicts. It can be saved for future reference.