-
Suggestion
-
Resolution: Duplicate
-
None
-
None
.I like the Shared Repository functionality - it solves one of the pains.
I would love to have similar functionality for credentials.
We have multiple repositories on BitBucket that I would actually like to be accessible from Bamboo.
Current solution that we have is set up a dedicated user, invite it to the repository, ask the guy who created the user what the private key/password is and create new repository.
It would be much easier and straightforward if I could just define those credentials globally and select them when configuring the repository.
The security implications would be basicly the same as for shared repository (ok, now I would be able to access any repository instead of just the ones defined as Shared)
- duplicates
-
- Closed
[BAM-10885] Shared credentials as extension to shared repositories concept
| Workflow | Original: JAC Suggestion Workflow [ 3014776 ] | New: JAC Suggestion Workflow 3 [ 3601196 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2701318 ] | New: JAC Suggestion Workflow [ 3014776 ] |
| Issue Type | Original: New Feature [ 2 ] | New: Suggestion [ 10000 ] |
| Workflow | Original: Bamboo Workflow 2016 v1 [ 1417628 ] | New: Confluence Workflow - Public Facing v4 [ 2701318 ] |
| Workflow | Original: Bamboo Workflow 2014 v2 [ 614804 ] | New: Bamboo Workflow 2016 v1 [ 1417628 ] |
| Workflow | Original: Bamboo Workflow 2014 [ 600059 ] | New: Bamboo Workflow 2014 v2 [ 614804 ] |
| Workflow | Original: Bamboo Workflow 2010 [ 364584 ] | New: Bamboo Workflow 2014 [ 600059 ] |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Description |
Original:
I like the Shared Repository functionality - it solves one of the pains.
I would love to have similar functionality for credentials. We have multiple repositories on BitBucket that I would actually like to be accessible from Bamboo. Current solution that we have is set up a dedicated user, invite it to the repository, ask the guy who created the user what the private key/password is and create new repository. It would be much easier and straightforward if I could just define those credentials globally and select them when configuring the repository. The security implications would be basicly the same as for shared repository (ok, now I would be able to access any repository instead of just the ones defined as Shared) |
New:
.I like the Shared Repository functionality - it solves one of the pains.
I would love to have similar functionality for credentials. We have multiple repositories on BitBucket that I would actually like to be accessible from Bamboo. Current solution that we have is set up a dedicated user, invite it to the repository, ask the guy who created the user what the private key/password is and create new repository. It would be much easier and straightforward if I could just define those credentials globally and select them when configuring the repository. The security implications would be basicly the same as for shared repository (ok, now I would be able to access any repository instead of just the ones defined as Shared) |