Instead of discovering the password by trying every one in the credentials, allow a credential to be assigned to a device.
The problem I am having is reuse of username per device vendor. Some devices only allow certain names (e.g. root, manager, admin, et. al.). Unimus' credential list shows the username, password (masked), and used by count. Should one device password change, it is impossible to know exactly which credential to change on Unimus.
[Implemented] username:password to device assignment
The current system is in place because in big deploys manual password management for devices is not scalable.
So you can just add all your credentials into Unimus, and it will just work.
We already have a feature request to allow specifying specific credentials per device, but the plan was for that to still be from the credentials list. So you would not type it in, but select one of the existing credentials to always be used on a particular device:
https://tracker.unimus.net/browse/UN-251
Is that enough for what you need?
Maybe a "Show password" button would also help?
So you can just add all your credentials into Unimus, and it will just work.
We already have a feature request to allow specifying specific credentials per device, but the plan was for that to still be from the credentials list. So you would not type it in, but select one of the existing credentials to always be used on a particular device:
https://tracker.unimus.net/browse/UN-251
Is that enough for what you need?
Maybe a "Show password" button would also help?
What you describe in a prior feature request would work; however, the username should not be the reference key because of username reuse (depending on vendor).
For example: How would one know which password to change or use if the key username is admin?
For example: How would one know which password to change or use if the key username is admin?