We recently enabled SCIM provisioning for our SonarQube Cloud Enterprise after having SAML SSO already configured and working. Our existing users were created through SAML and were already using SonarQube Cloud successfully. After enabling SCIM, we observed the following behavior: SCIM does not ma…

Hi @rafikagaoua , This is almost always an attribute mismatch. SonarQube Cloud identifies an SSO user by the value your IdP sends as the SAML login attribute (NameID). SCIM matches on userName. If those two aren’t the exact same attribute, in the same format and case, we see two different people an…

Hello Guillaume, Thank you for your response. I confirm that both the SAML NameID and SCIM userName are mapped to the userPrincipalName (UPN) in Microsoft Entra ID. It is worth noting that since enabling SCIM provisioning, new users assigned to the access group can access SonarQube Cloud without …

SCIM provisioning creates duplicate users instead of matching existing SAML users

SonarQube Cloud

sam.vimes (sam.vimes) August 11, 2026, 6:23am 6

Funnily, we have a similar but exactly opposite issue: SCIM does not create some users because they already exist. Same outcome, though: users lost access to projects.
@Guillaume_Peoch could this be related? Or just a coincidence?

Topic		Replies	Views
New users provisioned correctly, but not existing users with SCIM provisioning SonarQube Cloud saml , scim	1	61	May 11, 2026
SAML/SCIM creating duplicate accounts instead of linking to existing GitHub users (Enterprise) SonarQube Cloud github , sonarqube-cloud	0	121	June 24, 2026
SCIM - Groups Not Syncing Users Properly SonarQube Cloud	2	105	May 20, 2026
SCIM attribute mapping SonarQube Server / Community Build authentication	3	120	September 4, 2025
Mapping existing users with SAML plugin SonarQube Server / Community Build saml	2	1044	May 11, 2020

SCIM provisioning creates duplicate users instead of matching existing SAML users

Related topics