Continue synchronizing external directory after duplicate is hit

Problem Definition

When Confluence attempts to synchronize from an external directory and hits a duplicate that exists in the external directory-- like a user who is in two OUs that are within the scope of the filter. The remaining users in the directory are not Synchronized and instead just reported:

2018-03-23 18:13:04,980 ERROR [Caesium-1-1] [engine.jdbc.spi.SqlExceptionHelper] logExceptions ERROR: duplicate key value violates unique constraint "cwd_user_name_dir_id"
  Detail: Key (lower_user_name, directory_id)=(joanj, 3276801) already exists.

2018-03-23 18:13:05,055 ERROR [Caesium-1-1] [crowd.embedded.hibernate2.HibernateUserDao] addAll The following users could not be processed:
2018-03-23 18:13:05,056 ERROR [Caesium-1-1] [crowd.embedded.hibernate2.HibernateUserDao] addAll aliceb
2018-03-23 18:13:05,056 ERROR [Caesium-1-1] [crowd.embedded.hibernate2.HibernateUserDao] addAll christinej
2018-03-23 18:13:05,056 ERROR [Caesium-1-1] [crowd.embedded.hibernate2.HibernateUserDao] addAll Please try to resolve any errors with these users, and try again.

The directory synchronization is halted leaving all other users without issues out of the synchronization. This can result in new users not being synchronized to the directory because one user exists in two locations in the source LDAP directory.

Suggested Solution

Skip the duplicate user and allow remaining users that are not violating any constraints to be synchronized so that the impact of a duplicate in the source directory is lowered.

Workaround

Per our Confluence does not complete directory synchronization when a user is duplicated in multiple OUs article, remove the duplicate user or adjust the scope of the LDAP search exclude the duplicate.