Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,552,866
Community Members
 
Community Events
184
Community Groups

Restrict origin of users' SSH keys

Edited

We run Bitbucket Server (will soon "switch" to Bitbucket Data Center, as Server licenses are going away). Up until now, we have not enabled the bundled Apache Mina SSHD server to provide SSH access to Git repositories, but we want to do that. However, due to internal security restrictions, we cannot allow users to upload any arbitrary SSH key to their account. Rather, all the SSH keys we use within our organization are issued/signed by a central authority. So, we need to restrict the SSH keys that users upload to their accounts so that they are from this trusted source and not something they have arbitrarily generated on this machine.

Is it possible, in Bitbucket, to in any way restrict the keys that users upload? If not, we would not be able to use the SSH feature.

So, at the time I posted this, I had not been given all the information about what exactly we needed, so I did not ask the correct question...

Our organization-provided key pairs do not contain any kind of special data that identifies them as coming from our organization. So, what we actually need is a way to enable SSH key access for all users but permit only Bitbucket administrators the ability to add keys for the users (in other words, users would not be able to upload their own SSH keys). The Bitbucket administrators would be responsible for uploading the organization-provided public keys to Bitbucket.

Is this possible?

1 answer

So, at the time I posted this, I had not been given all the information about what exactly we needed, so I did not ask the correct question...

Our organization-provided key pairs do not contain any kind of special data that identifies them as coming from our organization. So, what we actually need is a way to enable SSH key access for all users but permit only Bitbucket administrators the ability to add keys for the users (in other words, users would not be able to upload their own SSH keys). The Bitbucket administrators would be responsible for uploading the organization-provided public keys to Bitbucket.

Is this possible?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events