How can I make the repository accessible only over the HTTPS urls? Including the cloning, fetching, pushing etc, ... all the operations.
Is there a way to remove the "SSH" clone option from clone button as well?
I'm afraid that it is not possible to either enforce HTTPS or remove the SSH option from the clone link in Bitbucket Cloud.
I can create a feature request for our development team to consider, please feel free to let me know if you would like me to do that.
If you don't mind me asking, why would you want SSH access disabled? I'm just asking to understand your use case better.
Hi @Theodora Boudale ,
Thanks for quick reply.
I'm looking for a use case, where...
From our organization, for some of the Atlassian accounts we want to have full control them on how they are accessing the repositories which they have been assigned to.
So, the passwords of their account are shared with them and they just need to use them. From the password manager we have shred this credentials. They can't see the password but they can copy and fill them. This way, the users don't need to remember them.
And the process of updating these access is easy and faster compare to maintaining the ssh keys.
Whereas as per my understanding, the ssh key is difficult to maintain and update in the machine.
So, to maintain the security, we just want user/ some group of user can access the repository over the HTTPS URL only. We don't want them to have ssh access any way.
I hope this has cleared your doubts. Let me know if you need more help.
Thank you for sharing more details and for explaining your use case.
I found out that we have a feature request for this already:
Please note that this request concerns managed accounts.
Managed accounts are accounts with an email from a domain that someone has verified, as per our documentation here:
In this case, organization admins are the ones that manage these Atlassian accounts, and they are the only ones that can e.g. delete an account.
If you'd be interested in that feature, I would suggest adding your vote in there (by selecting the Vote for this issue link) as the number of votes helps the development team and product managers better understand the demand for new features. You are more than welcome to leave any feedback, and you can also add yourself as a watcher (by selecting the Start watching this issue link) if you'd like to get notified via email on updates.
Implementation of new features is done as per our policy here and any updates will be posted in the feature request.
I also wanted to bring to your attention the following important change that is going to be implemented on 1st March 2022:
We will be deprecating the use of Atlassian account passwords when using Basic authentication with the Bitbucket API or Git over HTTPS. From that date on, users will need to create an app password and use that instead of a password when cloning/pulling from/pushing to Git repos via HTTPS.
This change already applies to any Bitbucket accounts that were created from 13th September 2021 onwards.
Please feel free to let me know if you have any questions.
Hi everyone, Are you Bitbucket DC customer? If so, we'd love to talk to you! Our team wants to dive deep to understand your long-term plans regarding Bitbucket DC and Atlassian Cloud. Do you plan...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events