Are NCM credentials a pain or am I missing something?
Login Credentials are easy enough to setup.
Device credentials can only be changed at the console? Like most folks, we use TACACS for most of our equipment and those accounts are independent of the Windows accounts. For security reasons, most of our users are not allowed direct NCM console access. At the same time, I don't want the NCM admins knowing the TACACS username and passwords for the unprivileged users. Anybody suggest a work around?
NCM Integration to NPM. On the Orion NPM Web pages, why do users require "view customization rights' to add NCM credentials? Maybe I did something wrong? Otherwise, I really can't afford to have every user who needs access to their configs to have the "view customization rights". (Yes, they have access to the NCM Web Console, but it sort of defeats the purpose of NCM/NPM integration.)
Any thoughts?