Loading...

XML

Word

Printable

Feedback Policy:

Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

When using Bamboo 5.6+ and Stash 3.2+ newly created Application Link with default settings:

The servers have the same set of users and usernames disabled
I am an administrator on both instances enabled

will result in application link created with:
Trusted Apps authentication disabled
OAuth authentication enabled:
- Allow 2-Legged OAuth enabled
- Allow user impersonation through 2-Legged OAuth disabled
Basic Auth authentication disabled

Please, make sure you have "Stash administration >> Settings >> Server Settings >> SSH access" configured as per following:

[x] SSH enabled
[x] SSH access keys enabled
SSH Port: 7999

When configuring repository definition on Bamboo side (either in "Plan configuration >> Repositories" tab or in "Bamboo administration >> Build resources >> Linked repositories") Bamboo will create SSH keypair and will store private key in the repository configuration and upload public key to Stash (it can be seen in the list of SSH keys of a user X who defined repository on Bamboo side).
When running a build Bamboo will present the private key thus making Stash recognise it as user X (independently on how plan was ran).

Instead of storing public key under the users' account, it would be beneficial storing it under the repository itself, avoiding the necessity of:

if a user is removed from Stash, it is required to redefine repository settings in Bamboo to new SSH keypair be generated
easier to manage repository permissions
Please let me know if you have any more questions related to this.

is duplicated by

BAM-14986 SSH key generated from Bamboo to Stash should be stored in project not in user profile

BDEV-9123 Loading...