You currently cannot do this in Stash as far as I'm aware. There is an open issue to disabling HTTP clone in Stash at STASH-2859. Although using HTTP is far more efficiant than SSH.
What are you reasons for wanting to disable HTTP?
If it's a security concern, you could look at setting up Stash to use HTTPS.
Stash 3.11+ has the option to disable HTTP for Git operations.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Security. Attacker could get access to website and add public key to user profile, or just clone from website. The first variant is harder. Second is possible.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
re: what are your reasons?
We want to prevent developers from updating the repository using HTTP with basic auth. We want to restrict all repository updates to using SSH so that we can avoid putting username and passwords on the wire.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.