Inherited shared to Personal Vault Structures in Devolution Server

Resolved

Inherited shared to Personal Vault Structures in Devolution Server

avatar

Hi support members,

Setup

  • Devolution Server

    • Workspace

    • Remote Desktop Manager

Our shared vault contains the following tree structure

  • [Relation A] - [General Shared Credentials]

  • [Relation A] - [Site] - [General Shared Credentials]

  • [Relation A] - [Site] - [Production Line A]

  • [Relation A] - [Site] - [Production Line A] - [...]

  • [Relation A] - [Site] - [Production Line B]

  • [Relation A] - [Site] - [Production Line B] - [...]

  • .....

  • [Relation B] - [General Shared Credentials]

  • [Relation B] - [Site] - [General Shared Credentials]

  • [Relation B] - [Site] - [Production Line A]

  • [Relation B] - [Site] - [Production Line A] - [...]

  • [Relation B] - [Site] - [Production Line B]

  • [Relation B] - [Site] - [Production Line B] - [...]

  • ........

.............

In addition to the shared credentials in the shared vault, each user has their own personal credentials (specific to these relations). These relationships are linked via "User Specific Settings," and this setup works well.

However, it is now common practice for engineers to duplicate this shared tree structure into their personal vaults. This approach is both labor-intensive and error-prone.

Question

Is there a way to partially or fully inherit the tree structure from the shared vault?

What would be another suitable setup that avoids placing personal credentials directly within the shared vault items? This is important because if an item is removed, the personal credentials would also be lost.

Thank you in advance for your help!

Rob

All Comments (4)

avatar

Hello,

Thank you for reaching out!

My name is William and I'm here to assist you in any way I can.

If all engineers are using RDM, I would suggest using My personal credential and My Privileged Account setting in RDM. You can find these settings under File > My account settings:

These settings are local to the RDM installation and can be configured just like a normal credential entry.

Afterward you can change the shared vault to use My personal credential and My Privileged Account. If the entries must be linked to specific accounts in the shared vault, engineer can also right-click on the entry and select Open with parameters where they will find the open with My personal credential and My Privileged Account.

Feel free to reach out if you have any questions or need further clarification.

Best regards,

avatar

Hello,

Thank you for reaching out!

My name is William and I'm here to assist you in any way I can.

If all engineers are using RDM, I would suggest using My personal credential and My Privileged Account setting in RDM. You can find these settings under File > My account settings:

These settings are local to the RDM installation and can be configured just like a normal credential entry.

Afterward you can change the shared vault to use My personal credential and My Privileged Account. If the entries must be linked to specific accounts in the shared vault, engineer can also right-click on the entry and select Open with parameters where they will find the open with My personal credential and My Privileged Account.

Feel free to reach out if you have any questions or need further clarification.

Best regards,

Hi William,

Thank you for your help.

I’m indeed familiar with this solution, and it would work well within an organization.

Our engineers have personal accounts with various external organizations.

This can easily add up to as many as 100 personal credentials per engineer (with or without OTP).

In such cases, this solution would not be feasible.

Kind regards,

Rob