-
Bug
-
Resolution: Fixed
-
Low
-
None
-
1
-
Severity 3 - Minor
-
Issue Summary
When using SSH key authentication, a confusing error can appear in the UI or logs if the incorrect SSH key format is used.
Example Steps to Reproduce
- Create an RSA SSH Key Pair using ssh-keygen
ssh-keygen -t rsa
- Add the Public Key to your Bitbucket Cloud account
- Upload the Private Key to a Linked Repository configuration
- Test the repository connection
Expected Results
The connection test is successful
Actual Results
The connection test fails, and the following exception is thrown in the UI:
Cannot decode connection params.
Notes
This occurs when the version of OpenSSH has RFC4716 as the default key format.
The SSHJ Library that Bamboo uses does not support the SSH2/RFC4716 keys.
Workaround
Create the key using PEM format, which RFC4716 replaced. For example:
ssh-keygen -m PEM -t rsa
Form Name |
---|
[BAM-20246] SSH Key authentication fails when RFC4716 format Keys used
Workflow | Original: Bamboo Workflow 2016 v1 - Restricted [ 3083304 ] | New: JAC Bug Workflow v3 [ 3386203 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Assignee | New: Pawel Skierczynski [ pskierczynski ] |
Component/s | New: SCP and SSH tasks [ 20391 ] |
Fix Version/s | New: 6.9.0 [ 85198 ] |
Labels | New: bamboo-bugfix-kanban-candidate |
Occurrence Factor | New: 10% [ 12830 ] | |
Symptom Severity | Original: Severity 2 - Major [ 15831 ] | New: Severity 3 - Minor [ 15832 ] |
Status | Original: Needs Triage [ 10030 ] | New: Open [ 1 ] |
Support reference count | New: 1 |