Feature Request: Support Variables from Linked Credentials in Entry Names

Feature Request: Support Variables from Linked Credentials in Entry Names

1 vote

avatar

Description

Currently, variables such as $USERNAME$ can only be used when the username is embedded directly in the session entry.
Many environments use Linked (Vault) Credentials to centralize credential management. In these cases, the linked credential already contains the username, but variables like $USERNAME$ are not available for use in entry names or naming templates.
It would be very helpful if Remote Desktop Manager could resolve and expose selected fields from linked credentials (for example $USERNAME$) so they can be used in entry names and other dynamic naming scenarios.

Use Case

We use linked credentials extensively to avoid duplicating usernames and passwords across multiple entries.

For example, it would be useful to create entry names such as:

  • Server01 - $USERNAME$
  • VPN - $USERNAME$
  • SQL - $USERNAME$


where the username is automatically pulled from the linked credential.
This would improve consistency, reduce manual naming efforts, and make entries easier to identify when multiple accounts are used for the same target system.

Expected Behavior

When an entry references a Linked (Vault) Credential, variables such as $USERNAME$ should resolve to the corresponding value stored in the linked credential, just as they do when credentials are embedded directly in the session.
Thank you for considering this enhancement.

All Comments (3)

avatar

Hello,

Just to get an idea of your environment, what type of credentials are you referencing in your entries?
The reason why certain variables like $USERNAME$ aren't resolved in names and other "dynamic" contexts is because of possible performance issues, since the application would need to resolve the credential linking of potentially dozens of entries to properly show the name in the tree. So, if you're using external credentials (LastPass, 1Password, etc), it would definitely not be possible as performance would slow to a crawl.

Regards,

Hubert Mireault

avatar

Hi Hubert,

I am referencing to a credential entry in the same vault. In my case I have a folder at the top of the vault with general credentials used in more than one entry to which I am referencing in session entries in the same vault.

Hope this makes it clearer.
Thank you for your effort.

avatar

Thank you for the information. I will open a ticket and we will see what we can do.

Regards,

Hubert Mireault