I hope there is not similar feature request, I could not find it. Maybe it would be useful to others too, that have "mass binding" requests.
What we "need" is ability to reorder priority of credentials used. If I understood, during discovery they are used from top to bottom and first one working is used for that device. Problem we have is with "read only" credentials that older ones are used and migrating to new ones is harder since we have weird case where we have 2 different central AAA servers with slightly different configuration. So we need to bind per device. Seems like simple feature to implement if not mistaken, since other places you have "reordering possible".
Thanks in forward
Device credentials priority
I would like to add this feature request.
Why Unimus needs to test all the credentials when the device has been discovered before?
Would it be possible to soft-bind the credentials that worked at initial discovery to device. That way you do not need to the bruteforce with all the known credentials to the devices. If the soft-binded credential does not work anymore then maybe try all the credentials?
The current discovery process is firing always up so many SIEM alerts and we end-up manually binding credentials to each device. This is tedious.
Why Unimus needs to test all the credentials when the device has been discovered before?
Would it be possible to soft-bind the credentials that worked at initial discovery to device. That way you do not need to the bruteforce with all the known credentials to the devices. If the soft-binded credential does not work anymore then maybe try all the credentials?
The current discovery process is firing always up so many SIEM alerts and we end-up manually binding credentials to each device. This is tedious.