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,457,046
Community Members
 
Community Events
176
Community Groups

Why I need to authenticate again with SSO to clone a new repo?

I have done my personal SSH keys on macOS settings. When I try to clone the repo in a new directory, I get the error:

git@bitbucket.org:Permission denied (publickey).
fatal: Could not read from remote repository

I thought my permissions was done once I configure the SSH key.

Thanks  

1 answer

1 accepted

0 votes
Answer accepted

Hi @jose_paredes and welcome to the community.

Your ssh client may not be offering the key you have added to your Bitbucket Cloud account, or the key may not be loaded to your SSH agent.

Can you try adding the following in the ~/.ssh/config file on your macOS (if the file doesn't exist, you can create it):

Host bitbucket.org
HostName bitbucket.org
PreferredAuthentications publickey
IdentityFile /Users/User/.ssh/id_rsa

where /Users/User/.ssh/id_rsa replace with the path and name of your private SSH key, whose public key is uploaded to your Bitbucket account.

Afterwards, try cloning again, and feel free to let me know how it goes.

Kind regards,
Theodora

Thank you, @Theodora Boudale !

Yes, the key was neither generated nor enabled in my SSH agent. I had to use the command: 

ssh-keygen -t rsa

And then copy the key type in "Selected SSH kyes" of my repo.

 

Regards,

Jose

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Atlassian Community Events