New users provisioned correctly, but not existing users with SCIM provisioning

SonarQube Cloud
,
1

Hi,

We are attempting to integrate SCIM provisioning for SonarQube Enterprise at Abbott using Microsoft Entra ID.

We are encountering an issue specifically with existing users:

  • Our environment previously used SAML authentication, where the user login attribute was set to samAccountName.

  • To support SCIM provisioning, we updated the SAML configuration to use userName instead.

  • SCIM provisioning has been successfully enabled.

  • New users are provisioned correctly via SCIM.

  • However, existing users are not being synced and are not linking to their existing SonarQube accounts.

We would appreciate guidance on:

  • How existing users can be successfully matched or migrated after changing the SAML login attribute

  • Whether a specific attribute mapping, user update, or re‑provisioning step is required

  • Any known limitations or recommended approach for handling existing users when enabling SCIM in this scenario

Thank you for your support.

We migrated from SAML login using samAccountName to userName to enable SCIM provisioning.

New users provision correctly, but existing users do not match.
Can you assist with updating existing user identifiers or advise the recommended migration approach to align SCIM identities?

2

Hello @Raupova ,

Thank you for trying out the feature.

Do you mean source attribute for the groups claim? Can you explain why you switched the user login attribute? If you change it back to sAMAccountName, do you still encounter problems?

Can you share a screenshot of where you changed this attribute? This will help me understand to check if I can reproduce the error.

Did you use this part of the SCIM documentation for Entra ID?