SSH keys are perfect when you control the private key. But sometimes you have to use that as a way to enable other systems to talk to bitbucket.
For example, if I want to use codenvy or devtable, i would have to upload a private key there, and a public key to bitbucket, so the tool can checkout code and commit for me.
But of course, i only want the tool (and its developers) to access the public repo i intend to use the tool on. Not my private repos.
My work around is to create a 'headless user' for the tool, upload the public key there, and give full permissions to it on the public repo i onw. But it would be easier for me and generate less useless accounts on bitbucket (not to mention prevent me from crossing some line in the UELA of the service) if i could restrict keys to repositories.
I know it sound like a feature request, and it probably is, but posting here in case there is a way to do that that i am overlooking.
Hi awesome community! In this article, I would like to describe the one of the toolset (service) for the analyze some problems on different Java-based instances, of course, as Atlassian admini...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs