I have a managed account (via Outlook) with which I am able to log in to bitbucket in my browser. I have created a repository but when I try to clone it, my password is not accepted: `fatal: Authentication failed for 'https://bitbucket.org/...`
I have added an SSH key to my account and that doesn't work either:
`email@example.com: Permission denied (publickey).`
(Note that the same key does work for firstname.lastname@example.org)
The only way I've got it to work was to create an App Password, but that is not an acceptable solution. I need to be able to authenticate via SSH.
This problem might be related to the following question, although SSH was not mentioned there: https://community.atlassian.com/t5/Bitbucket-questions/quot-remote-Invalid-username-or-password-amp-fatal/qaq-p/1076999
How can I get SSH authentication to work with my managed outlook account?
Hi @Quinten De Vos and welcome to the community!
If you use HTTPS, the account's password will not work for a managed account, and you will indeed need to use an app-password instead.
Since you want to use SSH, we can look into why this is not working for you.
Could you please share the verbose output of the following command from the machine where you set up SSH?
ssh -Tvvv email@example.com
This will show us verbose output and an indication of what may be going wrong.
I've run that command and the output can be found here: https://pastebin.com/9sGnqRm6
I have two ssh keys in my .ssh directory, which I would both expect to work as I have added them in the browser. (See screenshot) These are the keys that are shown in the logs on line 133 and 135 ("Offering public key: ")
(Offering public key:
Hi @Quinten De Vos ,
Thank you for your reply and the output.
Looking at the verbose output, the line that indicates the issue is the following:
debug1: send_pubkey_test: no mutual signature algorithm
after the public key id_rsa is offered.
Are you using Fedora 33?
The same issue is reported by other users who upgraded to Fedora 33 as this version has some changes in OpenSSH connections.
To work around this, you can create a config file in the .ssh folder and add the following:
Another option would be to generate a new SSH key pair with encryption algorithm Ed25519 or ECDSA and use that instead.
The algorithm is specified with the -t option, so you can use e.g. the following command to generate the SSH key pair
ssh-keygen -t ecdsa
Please feel free to let me know how it goes and if you need further assistance.
Announced in this blog, this holiday season we’re celebrating all things CI/CD and between now and the end of 2019 we’ll be showcasing content, use cases, feature announcements and more. One featur...
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