Organisation binding login loop after Bitbucket Forge migration — workspace UUID mismatch

SonarQube Cloud
1

ALM used: Bitbucket Cloud
CI system: Bitbucket Pipelines
Scanner command / repository languages: Not applicable to reproducing this issue; it occurs in the organisation settings UI.
Project URL: Private organisation; identifiers can be provided privately.

Error observed

After migrating the Bitbucket integration to Forge, opening Organisation Settings → Organisation binding causes repeated login redirects. Normal SonarQube Cloud login and other pages work.

The HAR shows this request repeatedly failing:

GET /api/alm_integration/show_bound_organization?organization=<redacted>
HTTP 401

{"errors":[{"msg":"User is not admin of the team"}]}

The current-user API confirms an authenticated session using Bitbucket.

We also found that:

  • Sonar’s /dop-translation/organization-bindings endpoint returns a binding whose workspace UUID differs from our current workspace UUID, verified using Bitbucket’s workspace API.

  • “View on Bitbucket” opens the stored UUID-based URL and returns “Resource not found”.

  • The Forge app is installed in our current Bitbucket workspace, and the old Sonar Connect app is no longer listed.

  • The Forge app settings show “Create new organization”. Refreshing connection status does not change this.

  • Sonar still displays the Forge migration banner.

Steps to reproduce

  1. Sign in to SonarQube Cloud using Bitbucket.

  2. Open the existing organisation.

  3. Navigate to Administration → Organisation Settings → Organisation binding.

  4. The page displays loading spinners, then redirects through login repeatedly.

Potential workaround

No workaround identified. Refreshing the Forge app’s connection status did not resolve the issue.

We have not created another organisation or changed the organisation key.

What caused the workspace UUID mismatch, causing the binding lookup failure and advise how to restore the existing organisation’s connection while preserving projects, analysis history and subscription?

2

Hey @sbahtiar, welcome to the Community! Could you please share the following?

  • Your organization key.
  • Both Bitbucket workspace UUIDs (both the one that you’re getting from /dop-translation/organization-bindings and the real one that you use (you mentioned they differ).
3

Hi,

SonarQube Cloud organisation key: elementalconcept-bitbuket

UUID from /dop-translation/organization-bindings : c2375e4b-7718-49c9-98b8-600794b01b9c

Actual Bitbucket workspace UUID : 276f86a4-3372-4fd9-aeae-acf7a2e65eef

6

Thanks @sbahtiar, the team is looking into it, they will let you know once they have more information.

7

Thank you.

9

Hey @sbahtiar, could you try again? The team has let me know that they have made the switch. It seems like this corruption of the binding happened due to the migration from the old Connect app to the new Forge app, as you suggested in your post.

10

Hi, It works! Thank you!