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,552,624
Community Members
 
Community Events
184
Community Groups

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

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.
Feb 09, 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