You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Is it possible that an access keys added to a repository R in a project A can conflict with same access keys added to a project B.
Because what I experienced looked like it, I was never able to clone a repository S from project B, the server kept returning Unauthorized, until I added that access key to S, then I cloned S successfully
Repository Access keys can be used across multiple repositories to provide read-only access, these can consist of the same public SSH key per-repository or can be different depending on individual need. For your purposes I would recommend sharing access keys between projects to ensure that access is granted between projects.
The only time a conflict should occur is if there is already an existing account-level SSH key configured in Personal Settings > SSH Keys - this cannot be used as a repository access key as it can't also be associated with an account:
Hope this helps.
- Ben (Bitbucket Cloud Support)