Option to Store Personal and Privileged Credentials in Database
1 vote
Hello,
On the "Account Settings" tab, where we configure all the different creds for various integrations that are supported, by default those will all be stored in the database unless we change the "save location" to "local". Having this flexibility to choose either option is very nice.
But the "my personal credentials" and "my privileged credentials" do not have the option to store in the database - they can only be stored locally. Is it possible we could add an option to allow these to be stored in the database if desired? So that way when we rotate our passwords we don't have to manually update them on each machine we run RDM from.
I was thinking before submitting this request about whether such an option might present a security issue, but I think if there's already confidence that credentials for all other integrations could be stored securely in the DB (including those to access various password management systems such as Keeper, which obviously hold very sensitive data), then there shouldn't be any reason that the "my personal credentials" and "my privileged credentials" couldn't be stored the same way?
I know we could just create a credential entry in the user vault and use that, but since we already make heavy use of the my personal/my privileged credential feature I figure it would be nice for those to work the same way as the rest.
Thanks in advance for the consideration.
Best regards,
David Willis
Hello David,
I think you bring up a great point. As you say, on the security side, there's no reason we can't store this information securely in the database, as we already do it with the "external credentials" part of this window.
Just a quick question, what type of data source are you using? SQL Server, DVLS, Hub?
Regards,
Hubert Mireault
Hi Hubert,
Sorry for the delayed reply. I am using SQL Server for a data source. Please let me know if you need any other info.
Best regards,
David Willis
Perfect, thank you for the information. I will open a ticket on our side and we will discuss this to see where it could fit on a roadmap.
Regards,
Hubert Mireault
Also I checked and just to clarify, this should already be supported with Devolutions Server and Hub, where they save in the database directly, since version 2025.1. For now my recommendation would be to migrate to Devolutions Server, but we will keep this in mind to be added to SQL Server too.
Regards,
Hubert Mireault