The users connecting to the Open Metadata via SSO for the first time getting an error that the “entity already exists”.

[Prajwal214]

When users connect to Open Metadata (OMD) via Single Sign-On (SSO) for the first time, they encounter an error stating "entity already exists." Here is a detailed breakdown of the situation:

Pre-Loaded Users: All users have been pre-loaded into OMD from Company Portal, including their email addresses, names, and departments.
SSO Authorization: Users are authorized in OMD using the same email addresses and names via SSO.
Registration Window: Upon SSO login, users see a registration window asking for their full name and department. However, the display name and email fields are not editable since they are already defined in SSO.

[Prajwal214]

Resolving "Entity Already Exists" Error in Open Metadata

Issue Overview

The "entity already exists" error typically occurs when a user tries to sign in via Single Sign-On (SSO), but their account already exists in Open Metadata with a different identifier or email format. This issue can arise due to mismatched email addresses or usernames between the SSO provider and Open Metadata.

Troubleshooting Steps

1. Check Email Consistency

   • Ensure that the email address used in the SSO provider matches exactly with the email address in Open Metadata. Any discrepancy can cause this error.

2. Principal Domain Configuration

   • Verify that the principalDomain in your Open Metadata configuration matches your organization's domain. This ensures that users are correctly identified.

3. User Import and SSO

   • If users are imported into Open Metadata before they log in via SSO, ensure that the email addresses used during import match the SSO email addresses.

4. Verify jwtPrincipalClaims

   • Check the configuration for jwtPrincipalClaims to ensure it includes the relevant claims for email and username:

     jwtPrincipalClaims: ${AUTHENTICATION_JWT_PRINCIPAL_CLAIMS:-[email,preferred_username,sub]}

Solution

The issue described has been fixed in the Open Metadata v1.4.5 release. Please upgrade to this version and verify if the problem persists.