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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Allow yarn/npm install for bitbucket repo for all teammates (ssh username issue)

Hi. We are a team trying to set up a private bitbucket repo to be used during yarn/npm install for all users.

The problem we are having is that some of our users have different ssh usernames for bitbucket, and so the connection fails.

For example, if I set up a npm module like this:

yarn add git+ssh://

 Some users cannot connect and download the module because they have a different ssh username associated at bitbucket, for example "". As a result they cannot connect.

We will not be able to share a repo as a npm module unless the url is the same for all users, of course, which seems to suggest we all have to have our ssh username be "". Can this ssh username be changed/reset independently using bitbucket settings?

Please advise how we can resolve this.

Thank you.

1 answer

1 accepted

0 votes
Answer accepted

Hello @Brendan Miller,

This sounds a bit strange to me. If you're using SSH, username in the repository URL should always be git (or hg in case of Mercurial repository). Users are identified by the SSH key provided.

The actual user's username is used only in the HTTPS clone URL, but that's irrelevant for what you're trying to set up.

Hope this helps. Let me know if you have any questions.


Thanks @Daniil Penkin  for your suggestion. After your post, I confirmed with a user who was having a problem and it does seem that they have never set up a SSH key for accessing their bitbucket repos and have always been cloning using HTTPS, which of course requires their username in the HTTPS link. That is the real source of the problem, it seems.

So I think the solution is to confirm that our users are all using SSH to access our repos and then I think the issue will resolve itself.

Like Daniil Penkin likes this
jredmond Atlassian Team Dec 03, 2019

You should actually be able to use SSH with the username, assuming the user has permissions and SSH keys set up appropriately. "" still works, though, and it's a good generic choice for individual users (and the only option for access keys).

Like Daniil Penkin likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

Powering DevOps with Bitbucket Server & Data Center

Hi everyone, The Cloud team recently announced 12 new DevOps features that help developers ship better code, faster   ! While we’re all excited about the new improvements to Bitbucket ...

2,119 views 0 7
Read article

Community Events

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

Events near you