SSH Terminal with personal SSH Key (stored in Bitwarden)

Hi Michael,

Thanks for the detailed write-up, it makes this easier to diagnose.

A couple of things before I can point you to the exact fix:

1. Which RDM version and platform (Windows, Mac, or Linux) are you running?
2. What workspace are you using (Team, DVLS, SQL, Cloud)? If it's DVLS, which version?

A bit of context: fetching SSH keys directly from Bitwarden (not just login credentials) is a newer capability in RDM. On older versions, linking an SSH Terminal entry to a Bitwarden item only pulls username/password, not the key itself, which is why you keep getting a password prompt. Once we know your version, we can confirm whether you have that capability and walk you through the correct setup for the SSH key and the username.

Also, the Privileged Account option you tried in Scenarios B and C is unrelated to Bitwarden. It pulls PAM accounts from Devolutions Server, so it only works if you have DVLS with PAM configured.

For reference:

• SSH terminal entry settings: https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/ssh-terminal
• SSH key entry settings: https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/ssh-key
• Bitwarden integration: https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/bitwarden

Looking forward to your reply.

Best regards,

Hi Alexis,

RDM-Version is 2026.2.17.0 64-bit
DVLS (self hosted) is: 2026.2.15.0

If i use specific ssh keys for specific connections (like dedicated shared users in our team) it works ; But not for my personal ssh key for personal conenctions.

Hi Michael,

Thanks, that confirms your version isn't the issue: Bitwarden SSH key support has been available since well before 2026.2.17.0 / DVLS 2026.2.15.0.

The fact that your shared/dedicated SSH keys work but your personal one doesn't points to a difference in how the entry is set up, not a version problem.

One clarification: "Privileged Account" (which you tried in Scenarios B and C) pulls PAM accounts configured in DVLS. It's unrelated to Bitwarden, so it won't work for a personal Bitwarden-backed key.

Could you tell us how the working shared SSH key entries are set up? Specifically, in the SSH Keys tab, what Entry type is selected, and if it's Linked (vault), whether the picker is set to SSH key mode rather than Credential mode when you select the Bitwarden entry. If you set up your personal key the same way (instead of through My personal SSH key or Privileged Account), it should behave the same as the shared ones.

Reference:

• SSH key entry settings: https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/ssh-key
• My account settings: https://docs.devolutions.net/rdm/ribbon-menu-bar/file/my-account-settings

Best regards,

Of course:

Here is a working example. We're using this setup cause we've specific users who should run the connection by one specific user (with key).

For the "username"-part we've defined the Username by a custom field in our global Bitwarden-Connection:

This works really well.

As written, the problem exists withhin my personal access to some SSH Terminals where everybody has it's own Username and SSH Key. It work's if i place the ssh key in the Bitwarden tresor or link it to a local file on my notebook (with passphrase ;)). But to get more secure here i would like to have also my own SSH key in my bitwarden vault incl. my personal username.

I think the best would be if i could select the bitwarden entry at this point: