Mremoteng: MR-184: Feature request: Credential repository

[viandham]

I would like to suggest a credential repository, so we can reference a specific set of credentials for each connection.
I, for example, have > 100 servers added in a specific windows domain. Password policy kicks in and forces me to update my passwords, now 100 entries are faulty. Instead, with a credential respository, I would update the master credential and this would apply to all linked connections.

Otherwise, thanks for a great application!

[smalla]

Hi,

This is already possible, with setting up inheritance on the tree.
I do have six domains, a few hundred servers, and change password only once
per domain.

Regards

1. okt. 28. du. 1:45 ezt írta ("Andreas Hammargren" <
   [email protected]>):

I would like to suggest a credential repository, so we can reference a
specific set of credentials for each connection.
I, for example, have > 100 servers added in a specific windows domain.
Password policy kicks in and forces me to update my passwords, now 100
entries are faulty. Instead, with a credential respository, I would update
the master credential and this would apply to all linked connections.

Otherwise, thanks for a great application!

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mRemoteNG/mRemoteNG/issues/208, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYFTi2d2ogtLP6wsXZPPfvaISsgH3hrks5q4eBfgaJpZM4KjWsS
.

[viandham]

Wow, I had no idea. Just found the "inheritance" icon, I had no idea it was there, and I have been using mRemote for so many years..

Well, then maybe I would suggest this feature to be more intuitive and easy to find then :)

Thank you!

[sparerd]

Adding to this, a true credential manager feature is in the works for v1.76 (the release after next).

[kmscode]

JIRA ticket: https://mremoteng.atlassian.net/browse/MR-184

[kmscode]

Export from JIRA:
MR-184.docx

[sparerd]

This feature is mostly complete and will be included in the v1.76 alpha (whenever that happens). There are some pretty important features that still need to be included before it can be used for production sysadmin work.

[sparerd]

I'm going to try to break apart the final implementation details of the credential manager to smaller pieces that need to be completed for this feature to be rolled out to the public. If anyone would like to help out with the implementation, I highly encourage it. Pull requests are awesome! Just give me a heads up so I don't duplicate your work.

Work that needs to be done

• [x] #659
• [ ] #660
• [ ] #667
• [ ] #672
• [x] #673
• [x] #680
• [ ] #1289
• [ ] #1364

We will also need general testing done after these known-bugs are worked out.

[codearoo]

Just adding comment and closing my other request as it's similar:
Passwords right now are saved encrypted into this XML file. It's nice we can export without the passwords, but it might be safer if we had an option to store the passwords using Windows security method.. or somewhere in the registry.

721

[codearoo]

187 Adding this ref too.

[sparerd]

Pushing this back to v1.77. The feature is not ready for production use and we have other features and fixes that need to be released sooner

[AndrewSav]

There are a lot of different secret storages out there thycotic secret server, Hashicorp Vault, Ansible Vault. One would prefer store their secrets in a backend they are already using for secret storage.

Thus it would be very nice feature if mRemoteNG Credential Manager could store secrets in this and other popular secret backends.

[ghost]

Would be ideal for it to also look in Windows Credential Store that is local on all Windows boxes.

[sethmgray]

What is the status on credential manager? Following the links around MR-184 mentioned above seems to lead to an endless loop of resolved duplicates...

We are looking (somewhat desperately) at a solution that will enable source controlled connections file that can be shared around a team. This, obviously, requires creds to be separated from that file...

[sparerd]

I'm starting the work of reapplying the credential manager feature to the develop branch. It was reverted for the v1.76 release because it was not ready for production.

[mrPsycho]

hashicorp vault is great option.

[35niavlys]

I think the feature doesn't go in the right direction. Current ICredentialRepository have to load all credentials in a list, I was expecting:

• a function to get multiple credentials from the server name
• a function to get the credential from a couple of server name/user
  It allows to request an HTTP service for example

[KUGA2]

What is the status on this feature?

I personally do not need a connection to a service, of even the encryption of the stored credentials.
Could you maybe split this feature up and release it step by step?

But, honestly, the inheritance feature is just good enough.

Note: The functionality of Terminals credential manager would be sufficient for me, and probably for most people, as a first step.