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
Given the limitation of the access key that it doesn't require a passphrase and cannot be associated with an account. It can be the case that one still have the read access of the private repository after his/her account revoked. Or worse, the leaked private key can causes an unauthorised third party gains access to the private repository.
Is there a way to
Hi @Jin Yu Tung,
Thank you for reaching out to the community.
Right now, there's no feature to manage repository Access keys' by setting policies such as rotating it periodically, or set an expiration, or controlling the creation.
We do have an existing feature request similar to it that can be located through this link. - https://jira.atlassian.com/browse/BCLOUD-21080
You can upvote and watch it for now so that you'll be notified of any updates from our team when the feature becomes available on Bitbucket Cloud.
For now, you'll have to manually rotate repository Access keys periodically by removing and generating new SSH keys.
For the workflow recommendation, I would recommend using the user's personal SSH keys instead and then managing their read access to the specific repository or workspace user groups.
This way, whenever a user is revoked, the SSH key will also be revoked.
Hope it helps and do let me know if you have further questions.
Hi @Jin Yu Tung
Right now, only admins can create repository Access keys and there's no feature to restrict admins from creating an access key.
However, as long a user only has Read or Write access to the repository, they won't be able to create Access keys.
Let me know if you have further questions.