WinSCP not working with inherited credentials // 2024.3.14.0 64-bit

Hello Tobi,

Thank you for reaching out to us regarding this,

• Could you please specify the version of RDM you are currently using?
• What type of data source are you using?

Let me know,

Best regards,

Hi Samuel,

Sorry, I put the version in the subject: 2024.3.14.0-64bit Enterprise
As data source we are using MSSQL.

Best Regards,
Tobi

Hello Tobi,

Thank you for your reply,

No problem, I will attempt to reproduce the issue on my end and keep you updated with any news I have,

Best regards,

Hi Samuel,

Thank you very much!

Best regards,
Tobi

Hello Tobi,

Thank you for your patience,

I've not been able to reproduce the behavior on my end using the latest version of RDM 2024.3.15.0.

Could you confirm if you're still having the issue after the upgrade?

If you are, can you confirm which option you are using in the "Entry Type" field of the "SSH Key" section of the "WinSCP" entry properties?

Let me know,

Best regards,

Hi Samuel,

Thanks for your feedback, yes even with the latest version 2024.3.15.0 I have the issue.
All SSH Key parameter are empty because it's inherited from the main SSH connection.

I've attached some screenshots, maybe it's better to understand ;-)



My personal credentials - SSH-Key (used in SSH connection as credentials):



Navigation overview:


Folder and Server settings (Name + Host + IP):


Main SSH Connection (Host = inherited / Credentials = linked credentials) // nothing more


SSH-Key section is empty:


WinSCP entry (host = inherited / credentials = inherited / +some parameter):


WinSCP SSH-Key section (empty):



Thank you!!

Best regards,
Tobi

Hello Tobi,

Thank you for your reply,

When the "Credentials" field is set to "Inherited" this does not include the "Private Key" configuration I suspect this is why you're encountering this issue, you would need to change "Entry type" of the "SSH Key" from "No Private Key" to your preferred method.

Let me know,

Best regards,

Hello Samuel,

This kind of setting we are using over the last two years, so it works like a charm until one of the last RDM updates.

The ssh connection is linked to my personal credentials. My personal credentials holds my ssh key and the passphrase.
So every sub connection ( like WinSCP) also using this ssh key (Inherited).

This settings (inherited creds) still working for the SFTP connection. But not for the WinSCP connection.

Greetings,
Tobi

Hello Samuel,

I wasn't able to download an older version of 2024, because only the previous release (V2024.3.15.0) is available (https://devolutions.net/remote-desktop-manager/home/previousversions/).
But I've downloaded a version of 2023 (2023.3.35.0 64-bit) and with this version the connection with both inherited settings is working.

Is there a way to download a version of 2024 from maybe July to find the version with the change?


Best regards,
Tobi

Hello Tobi,

Thank you for your reply,

Are you looking for a specific version? the earliest version of 2024.3.x is 2024.3.10.0 and can be downloaded from here:
2024.3.10.0

I would recommend against connecting to your SQL Server data source using an older version than 2024.3.x as it could cause issues.

Best regards,

Hi Samuel,

I'm sorry for the delay, but at the moment I don't find time to test with the old RDM versions.
But .. with version 2024.3.19.0 64-bit the bug was fixed and I can use WinSCP as described again.

Case closed ;)

Best regards,
Tobi

Hello Tobi,

Thank you for your reply,

No worries. I'm glad to hear this is working as expected.

Best regards,