Violation of UNIQUE KEY constraint "SIBLING_NAMES" after upgrade to RH-SSO 7.3.4

Solution Unverified - Updated -

Issue

  • See following error:

    Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Violation of UNIQUE KEY constraint 'SIBLING_NAMES'. Cannot insert duplicate key in object 'xxxx.KEYCLOAK_GROUP'. The duplicate key value is (xxxx, <NULL>, xxxx).

Environment

  • Red Hat Single Sign-On (RH-SSO)
    • 7.3.4
  • Microsoft SQL Server Database (MSSQL)
  • Lightweight Directory Access Protocol (LDAP) or Microsoft Active Directory Lightweight Directory Service (AD)
  • LDAP configuration has a group-ldap-mapper
  • Upgrade to RH-SSO 7.3 CP4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content