I have a workaround in place for this:
- Created a Configuration Group and added the required CLI templates and Virtual Domain devices. Users have read only and deploy access so they cannot modify the Configuration Group prior to deployment
- Unfortunately, users still have access to Configuration > Templates > Features & Technologies which allows them to select any System Defined CLI template and deploy it on any of the Virtual Domain devices. I got round this by removing access the TACACs attribute "task11=Configure Menu Access" so the users cannot access the Configuration menu.
- To access the Configuration Group, users use the search bar to search for "Configuration Group" - this takes the user directly to the Configuration Group where they can deploy only the selected templates.
Its not perfect but seems to work. Does anyone have any better designs?
Thanks
Andy
Authenticated user's TACACs attributes are below:
virtual-domain1=CAMPUS
role0=User Defined 1
task2=Deploy Configuring Access
task3=Configuration Templates Read Access
task4=Monitor Menu Access
task5=Help Menu Access
task6=Device Reports Read Only
task7=Saved Reports List Read Only
task8=Reports Menu Access
task9=Run Reports List
task12=Search Access
task13=Tools Menu Access
task14=Administration Menu Access
task15=Monitor Clients
task16=Home Menu Access