Open SCP Embedded connection issue with private keys in File, Data, Vault types.

Resolved

Open SCP Embedded connection issue with private keys in File, Data, Vault types.

avatar

"Open SCP Embedded connection" do not works with private keys in Private key types:

  • File
  • Data
  • Vault


"Open SCP Embedded connection" works with password authentication fine!

For last version RDM on MacOS 2023.2.5.1 - SCP connections with keys works only at SCP Session with private keys published with SCP - Advanced - Use SSH authentication agent. In this case it works from both Actions: Open session (double click) and with menu "Open SCP Embedded connection".

Expected behaviour: at SSH session - action "Open SCP Embedded connection" should open SCP connection authenticated with private keys from File, Data, Vault types.

Current behaviour:
- at SSH session - action and menu item "Open SCP Embedded connection" do not open SFTP form and don't do any visible actions if configured private keys in File, Data, Vault types. Same time SSH session opens well.
+ at SSH session - action “Open SCP Embedded connection” works only with configuration menu item:

  • SSH Shell - Private Key - Private key type = No Private key ( mandatory because menu item "Use SSH authentication agent" action ignore "Private Key" to prevent keys conflict - not correct ignore )
  • SSH Shell - Advanced - Use SSH authentication agent
  • SSH Shell - Advanced - Allow SSH authentication agent forwarding.
  • Private key in Credentials resource published with Private key - Advanced - Automatically load to SSH Key Agent.


All Comments (4)

avatar

Hello,
We already have a ticket opened that seem similar to the issue you have.
We are looking into the problem but we sadly don't have an ETA on when it could be solved.
If you have any question, don't hesitate to ask.

Best regards,

Michel Lambert

avatar

Hello vagursky,
We were wondering if you can update latest version available and see if you still can reproduce the problem?
An issue that was solved on that version might have also solved your problem.

So if you can just confirm if you still have the problem or if it is solved, we would really appreciate it.

Best regards,

Michel Lambert

avatar

Hello vagursky,

We just came upon something and we were wondering.
Is your private key protected by a passphrase?
If yes, is saved on the entry itself?

It might help us to know.

Best regards,

Michel Lambert

avatar

Hi. I have 2023.3.32.0 running.
Private key is saved directly in the entry, as well as the passphrase.

If I open the entry with embedded SCP, it still tries to use password authentication.