Resolved SSH Key Manager -- PLEASE give details of acceptable format for public key

[MHC_1]

Server operating system version

Alma Linux 9

Plesk version and microupdate number

Obsidian 18.0.3

The SSH Key manager claims to be able to use SSH Keys for domain account connection.

I have been having issues with the "incorrect format" for the keys; Without any guidance on what is the desired format:




AND


But there's no details given either here or on any documentation that can be found.

Things also tried:

- Have removed all spaces from key text
- Have removed all text that is not the core key
- Have copied and pasted the complete key file contents
- Have shaped the key text starting with <key-type><space><keytext>

but all of these also fails.
None of this works.


WHAT IS THE CORRECT FORMAT FOR PUBLIC SSH KEYS COPY/PASTED FROM EXISTING TEXT FILES

Please also update the Plesk documentation with this as we couldn't find this information anywhere.

 

[MHC_1]

Further to the above; the documentation here:

https://support.plesk.com/hc/en-us/articles/12377016552727-How-to-provide-access-to-domain-in-Plesk-via-SFTP-using-SSH-keys-instead-of-passwords

The guidance "4.3. Paste your Public Key (*.pub) and press Add button." is Wrong . This is the problem.


All our Keys were generated in Putty.

 

[MHC_1]

Ok

Solution:
After much trial and error I have established

Format MUST be:

<key-type><space><key-text-no-line-breaks><space><title-text>

All parts of this are required and no line breaks can be in the text. "Title" is required.

As mentioned elsewhere title text can be in quotes if it contains spaces.

 

[Matt2k]

Guys, come on. This is absurd. Put this in the feedback that the application gives you.

<keytype> <key> is a valid SSH key
<keytype> <key> <comment> is a valid SSH key
<keytype> <key> <comment with spaces> is a valid SSH key

Your system only accepts one of these 3

This is not unreasonable. This is really bad UX for a plugin that only does one very very simple task.

 

[SibProgrammer]

All the issues mentioned here were fixed in SSH Keys Manager 1.3.0.
One can submit the key generated by PuTTY (following RFC 4716):

---- BEGIN SSH2 PUBLIC KEY ----
Comment: "rsa-key-20260527"
AAAAB3NzaC1yc2EAAAADAQABAAABAQCUTT4LSKawmInM/CeLuGCHeuo/2MgHdYjp
7wU0sAxtC6XBh5+68/qN8OlaoBx/OwTwu6ilrfgAWn60WJyYwDE3NQbM1QivDZPh
...
---- END SSH2 PUBLIC KEY ----

Or in OpenSSH format:

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDaeS8YoGUeQGefq... user@host

Comments are optional, and a key identifier will be auto-generated if the comment is omitted.

 

[MHC_1]

All the issues mentioned here were fixed in SSH Keys Manager 1.3.0.
One can submit the key generated by PuTTY (following RFC 4716):

---- BEGIN SSH2 PUBLIC KEY ----
Comment: "rsa-key-20260527"
AAAAB3NzaC1yc2EAAAADAQABAAABAQCUTT4LSKawmInM/CeLuGCHeuo/2MgHdYjp
7wU0sAxtC6XBh5+68/qN8OlaoBx/OwTwu6ilrfgAWn60WJyYwDE3NQbM1QivDZPh
...
---- END SSH2 PUBLIC KEY ----

Or in OpenSSH format:

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDaeS8YoGUeQGefq... user@host

Comments are optional, and a key identifier will be auto-generated if the comment is omitted.

@SibProgrammer thanks. The core issue was not the code format for textual Key addition but the complete lack of documentation of this within the Plesk environment. Hopefully the update addresses documentation advising the correct key formats expected.