Bitbucket 7.21.19 will not provide valid OAuth responses to Linked Repository requests from Bamboo

Issue Summary

This is reproducible on Data Center:

Bitbucket 7.21.19 will not provide valid responses to Bamboo when Linked Repositories are requested via Application links and OAuth impersonation is used.

Affected Versions

• Bitbucket 7.21.19 (specifically)

Steps to Reproduce

1. Install Bamboo (tested on 9.2.7, 9.4.2 and 9.5.0-SNAPSHOT)
2. Install Bitbucket 7.21.19
3. Configure a common authentication (LDAP/Crowd/etc)
4. Configured Application Links between Bamboo and Bitbucket with OAuth impersonation
5. Try to add a Linked Repository in Bamboo

Expected Results

Bamboo should be able to list the available linked repositories without issues.

Actual Results

Bamboo fails to list available repositories from Bitbucket with the following messages:

• Selected server has no repositories.
• Repository could not be found. You don't have permission to see this repository. Bamboo can still access this repository at build time, but simply can't show you any details. Bamboo will continue to work without problems.

When adding a new repository in Bamboo, the list only shows public repositories from Bitbucket.

Workaround

• Use OAuth (without impersonation). That requires an extra step from a Bamboo Administrator to authenticate once per Linked Repository to fetch the information from Bitbucket