Secure Login cannot be updated due to "Violation of UNIQUE KEY constraint" error

Owned by Former user (Deleted)
Last updated: May 09, 2019
1 min read

Problem

Updating an old Secure Login version (older than 2.x) to a newer version (newer than 2.x) fails with the following error message:

Cannot insert duplicate key in object 'AO_xxxxxx_SECURE_LOGIN_USER'.

Solution

In the first versions of Secure Login it can happen that several user profiles for one user are stored in the database. With Secure Login 2.x this is no longer allowed. Duplicates must therefore be removed from the old database table so that the user profiles can be migrated when Secure Login is updated to a newer version.

As a system administrator complete the following steps to solve the problem:

  1. Shut down the application (e.g. Jira, Confluence, ...).
  2. Connect to the database using a database administration tool.
  3. Find the database table AO_xxxxxx_USER_CONFIG and delete all duplicates.
  4. Restart the application and start the update process of Secure Login again.

If this does not solve the problem, it is recommended to uninstall the old Secure Login version to reinstall the new version from scratch. All configuration data and user data will be removed. Secure Login must be reconfigured and reactivated. At the next login, all Secure Login users will be prompted to reconnect their authenticator through the onboarding process.