...
Input Name | Description | Input Type | Required |
|---|---|---|---|
SSH Key | SSH Key which will have its content stored in encrypted format. Before encrypting, FlexDeploy will convert all End of Line characters to Unix. This is to avoid any errors related to invalid format. | File | Yes |
Passphrase | Passphrase for accessing the SSH key (optional, also stored in an encrypted format). | Text | No |
...
Trouble Shooting SSH Key Credentials
Invalid Format
If there is an error when using an SSH Key credential that includes the message “invalid format” or sometimes “error in libcrypto”, then it might be possible that the key is not formatted properly when being used. This error commonly occurs when trying to connect to a GIT repository using a file that does not have Unix End of Line characters. When uploading an SSH Key, FlexDeploy will automatically convert all Windows and Mac EOL characters to Unix in the content before encrypting and storing in the database. However, if using custom workflow script or groovy script logic to manually use a private key, then this error might occur.
...
The correct format of a private key file must have Unix EOL characters, and must have an empty line at the end of the file. When you generate a private key using OpenSSH, then the resulting private key will have Unix EOL characters even if generated on a Windows machine. The screenshot below is an example of the proper EOL format. The actual key content itself does not matter, but notice the End of Line characters. You can enable the EOL symbols in Notepad++ by clicking View → Show Symbol → Show End of Line.
...
If copying the content of an existing private key to a new file then it may result in improper formatting. Here is an example of an invalid format which would cause the error shown above.
...
Similarly, the file may have Windows EOL characters which will appear as CR LF. To convert to Unix EOL characters in Notepad++, you can use Edit → EOL Conversion → Unix to correct it.
...
Permission denied (publickey)
...