Automatic data source configuration / assignment of credentials templates to users
Automatic data source configuration / assignment of credentials templates to users
1 vote
As we have many users that have RDM and Launcher client we would like to avoid manual configuration of data sources and credentials templates.
Can you look into option to implement this, to add additional switches in the installer, so that data source can be defined during the silent installation?
Can you include a way to push "mandatory" template to user groups? For instance, currently, user must manually import a template to his user vault. And if there is a change to the template, he needs to delete the current template and re-import a new one.
Currently our vaults do not contain any secrets. Users import credentials template to their user vault. The template holds secret lookups for Deliea PAM.
All Comments (6)
Hello,
Thank you for your request. Custom installers can be used to automatically set up the data sources. Here is the documentation: https://docs.devolutions.net/rdm/installation/client/custom-installer-service/custom-installer-manager/
Regarding your second request about having a mandatory template, could you explain more about what is needed? I understand that you want to set up your user's vault with pre-configured entries, am I correct? Also, do you wish to update these entries frequently ?
Best regards,
François Dubois
Hi Francois,
We are already using custom installers, would it be possible to add additional switches for msi packages?
As for the second point - exactly, we would like to have a way to push templates to user's vault.
To put more information about our use case:
We have multiple teams that have their dedicated vaults (only connections are stored in those vaults, no secrets).
For those teams we built different templates that hold shared service accounts ("Delinea secret server (Credential)"). As we are adding new connections (new server or device gets provisioned/installed) we often update templates with new shared service accounts, and then we need to notify the user, to delete the "old" template and import a "new" template where new accounts are added.
If there would a possibility to create templates, that automatically get deployed and updated to user groups, that would fit our needs. Preferably, the template would be "locked" for editing for the users - so that only DVLS administrators or specific group can edit.
Hello,
For the MSI package switches, it would be useful to know what kinds of switches you would need, and why the custom installer doesn't work for your needs?
You might also be interested in the concept of the default.cfg file, which is what the custom installer uses to give users their default settings. You can distribute this file through other means you see fit. This article in our knowledgebase is about installing RDM in a terminal service environment, but the usage of the default.cfg file described in there is applicable in a non-terminal-service environment to give users a default configuration: https://docs.devolutions.net/rdm/installation/client/terminal-services/#workflow
For the 'templates' in your user vaults, would it be possible for you to give an example of what the admin pre-configures, and what the user then enters themselves in the credential entries? Credential entries that link with third party services like the Delinea entries usually have the "Use my account settings" checkbox:
The goal of this setting is so you can store this entry in shared vaults, but every user using this entry would be logging into the service with their own credentials, rather than a set of credentials the admin provides. You can of course configure the entry to be in "always prompt with list" if the users would want to access a different list of credentials than their colleagues.
Can you let me know if this is something you already explored, and if so, what made it so you couldn't use it in your environment or why it made it more difficult to use than your current solution?
Regards,
Hubert Mireault