Missed Team ’24? Catch up on announcements here.

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

Git private key authentication fails with "BEGIN OPENSSH PRIVATE KEY" format

Peter Steiner Privat
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 5, 2019

I had troubles setting up a git repository against Gitlab.

The connection test failed with "Cannot decode connection params" while a test checkout provided the following error in the stack trace:

at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.IOException: unrecognised object: OPENSSH PRIVATE KEY

I found out that i needed to convert my key file to an older format that contains "BEGIN RSA PRIVATE KEY" instead of the "BEGIN OPENSSH PRIVATE KEY" my key file originally contained.

Since the original key file was created as per Gitlab instruction, and worked in many other scenarios (including a local shell git test with the bamboo user), I wonder if my setup is broken somehow? Please note that I use the official Bamboo docker container.

1 answer

0 votes
Gonchik Tsymzhitov
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 9, 2019

Hi! 

 

as workaround you can mount the authentication parameters into docker container :)

https://community.atlassian.com/t5/Bamboo-questions/Bamboo-Git-authentication-fails/qaq-p/329703

 

Hence you key will work

 

Cheers,

Gonchik Tsymzhitov

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events