Migrating SonarQube Cloud Authentication from BitBucket to GitHub

SonarQube Cloud
, , ,
1

We’re currently using SonarQube Cloud with authentication handled via BitBucket. As part of our SCM migration, we’re moving from BitBucket to GitHub and need to update our identity provider accordingly—from BitBucket to GitHub.

I’ve searched the forums and came across this post, which outlines a very similar issue. However, it’s a few years old now, and I’m unsure how much of it is still relevant; much of it seemed to be resolved in private threads.

Can anyone point me to up-to-date documentation or provide guidance on what steps are involved in switching the authentication method for SonarCloud users? Specifically, we’re looking to understand the implications for user accounts, permissions, and existing project associations.

Thanks in advance!

2

Hi,

To be clear, we’re not talking about SonarQube Cloud’s Enterprise SSO, but just logging in with BitBucket, right?

If that’s the case, there’s no real user migration. Each user will log in with GitHub and thus create a new account, requiring permissions to be re-established and issues to be reassigned.

 
HTH,
Ann