Problem Definition

When a user creates a Bitbucket Server or Data Center repository configuration ssh keys are automatically created by Bamboo and the public ssh key uploaded to Bitbucket. In short, if the user has permissions to manage the repository in Bitbucket, the public key will be added to the repository. However, if the user doesn't have permissions to manage the repository (only to access it) the public key will be added to his/ her own profile under Manage account > SSH keys in Bitbucket.

If the public key gets added to the user profile this might become a problem when that user is deactivated (i.e. user showing up as UNLICENSED) or deleted from Bitbucket. If the public key is not accessible anymore because the user is not available, Bamboo will fail to communicate to Bitbucket using that ssh key pair.

When a Bamboo admin attempts to re-save the repository configuration in an attempt to avoid running into this problem and change the location of the keys nothing happens. The location of the key does not change.

Suggested Solution

Allow Bamboo admins to re-save the repository configuration and change the location of the ssh keys in Bitbucket Server or Data Center to avoid problems accessing the repository if the user eventually gets disabled or deleted from Bitbucket. Since the public key location will change to the repository it will no longer be associated to a specific user account – so changes to that account will not affect the public key and the communication between Bamboo and Bitbucket for that repository.

Workaround

Ask the user who saved the repository configuration to remove the public key from his/ her user account in Bitbucket under the Manage account > SSH keys page so that you (as a Bamboo admin) can re-save the configuration and change the location where the public key is stored.