Key Agent Manager | Format not supported when the key type is data
Key Agent Manager | Format not supported when the key type is data
I am having some difficulty with importing a private key to the key agent manager automatically.
When I create a new private key and select the key type as data when I stop and start the key agent manager it comes with the error "The private key format is not supported by the Key Agent."
But if I change the key type instead of Data to File, it comes with no error when restarting Key Agent Manager and prompts me for preshared code
Running on Free Edition: 2021.2.21.0
Screenshot_3.png
Screenshot_2.png
Screenshot_1.png
All Comments (9)
Hello,
Thank you for contacting us on that matter!
Would it be possible for you to update to the latest version of RDM Free and see if the same issue occurs with it? This version can be downloaded here: https://remotedesktopmanager.com/home/thankyou/rdmfreesetup
Best regards,
James Lafleur
Hello,
I have the same issue on version 2022.1.23.0, on Windows. My keys get imported by the SSH Key Agent when they come from files, but not when they come as "data".
Hello,
Are you using the exact same private key both in "data" and "file" modes? Do you reproduce this issue no matter the private key you do this with, or is it only certain ones?
We haven't been able to reproduce this issue internally so we would need more information to figure out what is the issue.
Regards,
Hubert Mireault
Hi!
Yes, I am using the exact same private key both in "data" and "file" modes. The issue happens with all my keys, they are ed25519 keys in the OpenSSH format.
I can also manually add them to the key agent with no problem.
Hello,
Even with such a key, on my end I haven't reproduced and it loads correctly from a private key entry in "data" mode:
Would it be possible for you to generate a new private key that reproduces the issue and send it to me through the forum's private messaging system? It could help us pinpoint what exactly is the issue. Just make sure this key is not actually used in any actual authentication context.
Regards,
Hubert Mireault
Sure, I just created a new key pair, I will send it to you. Thank you for your time.
EDIT: I sent you the key pair.
Good news, I was able to reproduce the issue, and made a fix. This fix will be available starting with RDM 2022.1.25.0.
From what I found, it occurred only on Password Hub datasources. Until the fix, the workaround would be to link the private key entry directly in the SSH entry for example, or to use the "file" mode so they are properly loaded in RDM's key agent.
Regards,
Hubert Mireault
Hi Hubert,
I just downloaded the update, and awesome, it's indeed fixed!
Thank you for the fix and the great product,
Regards,
William Blondel
Thanks for the feedback William, glad it works for you!
Regards,
Hubert Mireault