"User with same name already exists with a different provider type" message occurs during failed OIDC login

Products

• VMware Cloud Director

Issue/Introduction

• Impossible to connect to VCD through OIDC Microsoft Azure Entra ID.
• Users can't connect through OIDC on VCD Provider access.
• On the Azure app, the logins are all "success"
• Within the Cloud Director log file /opt/vmware/vcloud-director/logs/vcloud-container-debug.log you observe
  
  2025-07-23 09:30:13,842 | DEBUG| pool-jetty-##### | OrgMemberProvider | User with same name already exists with a different provider type.
2025-07-23 09:30:13,853 | WARN | pool-jetty-##### | OAuthAuthenticationSuccessHandler | Error logging in user <user-id>

Environment

VMware Cloud Director 10.6.1

Cause

This issue will occur if the user has both an OIDC and SAML or LDAP record for their username in the Cloud Director provider Users page. Even though the SAML or LDAP configuration may have been removed when enabling OIDC, stranded records for the individual usernames can still exist in the user inventory if they had not been deleted prior to removal of the SAML or LDAP configuration.

Resolution

To resolve this issue:

1. Login to the Cloud Director Provider UI using the default administrator account. 
2. Navigate to "Administration -> Users" page.
3. Review the User Name records and confirm that there multiple entries for the user who cannot login. One entry is marked as OIDC provider type and the second marked as a SAML or LDAP Provider Type. 
4. Delete the secondary username entry which will be SAML or LDAP provider type.
5. Confirm that OIDC login works successfully for the user.