Add inheritance to advanced settings on RDP session

Add inheritance to advanced settings on RDP session

0 vote

avatar

Hello,

A client has requested an enhancement to add more inheritance options for RDP entry settings.
The client needed to update the Username format across a large number of RDP entries. Adding inheritance capabilities for such settings would allow for streamlined updates, saving significant time and effort when making bulk changes.



Best regards,

Jacob Lafrenière

8d378e6f-6fa5-42a6-8e47-0fca78c107c9.png

All Comments (2)

avatar

Hello,

A ticket has been created for this feature request.

We will update this thread on any progress made.

Best Regards,

Michaël Beaudin

avatar

Hello jlafreniere,

We currently already have 2 different ways you could achieve your goal.

  • The first one, is using the Batch edit feature. While having multiple entries selected in the navigation pane, you can right click to bring up the contextual menu, and use Batch edit - Edit entries (general settings). This will prompt a window where you can select various settings that will be modified in all targeted entries. (You can go in the Advanced section to change the Username format).
  • The second one, is the concept of "soft inheritance" that is already implemented for the username format. Having a credential entry with a specific username format set will transfer this format when used with linked sessions.
    • To clarify, here is an example: If you have a Website entry, with the username format set to No change. This Website entry has a linked Username/Password credential and this credential has the username format set to Username@domain. When using the credential with the Website entry, it will be under the Username@domain format. If you then change the website entry settings to Domain\user, it will be used under this format (and thus ignore the credential's entry format).


This should give you quick ways to change this setting for multiple entries.
We will consider adding inheritance as per your request, but this is not a simple change to implement without impacting currently existing configurations. We hope these options are acceptable workarounds for you.

Regards,

Jafran Majeau