@KoenV wrote:
@cjoseph wrote:
Compnerd,
You can open a TAC case for any fingerprints that don't appear in the database. We have to QA them before they are added, however.
Why isn't there an option to create your own fingerprints? Passing any and all such requests through TAC seems like a major waste of time? And honestly, what customer can wait for your QA process?
Gave kudos for your idea there compnerd.. maybe there is a valid reason why we can't add those fingerprints ourselves but thazt reason elludes me.
That is not true. It is much more than just adding signatures; there is a QA process to make sure that no other devices have the similar signature as well as put them into categories that can also be used in the auth process. Signatures are updated constantly and automatically in CPPM and it does not take months; it happens fairly quickly.
In my opinion, the majority of the users just want signatures to be there, correct and categorized properly. They do not want to be creating it themselves. On the controller side, identifying, creating and ensuring that duplicate devices do not have the same signatures takes some work, sometimes and can be frustrating. I would rather allow Aruba to qualify the signatures so that devices can be identified and categorized properly. For every user that wants to create their own signature, there are 100 that just want it to work properly.