What you are trying to do was applicable till LMS 3.x. From LMS 4.x onwards this changed as we don't depend on ACS anymore for authorization.
It would be correct to say that ACS developers removed that portion from ACS 5.x onwards where Integration between LMS and ACS was done for both Authentication and Authorization.
Now you can only have Authentication part from ACS as a RADIUS server, Authorization OR what role a user will have, needs to be configured on LMS itself.
So LMS 4.x onwards it has Role Based Access-Control (RBAC) inbuilt. It can have following Roles :
•
Help Desk—Can access network status information only. Can access persisted data on the system and cannot perform any action on a device or schedule a job which will reach the network.
•Network Operator—Can perform all Help Desk tasks. Can perform tasks related to network data collection. Cannot perform any task that requires write access on the network.
•Approver—Can approve all tasks.
•Network Administrator—Can perform all Network Operator tasks. Can perform tasks that result in a network configuration change.
•System Administrator—Can perform all system administration tasks.
•Super Admin—Can perform all operations including the administration and approval tasks.
You can also add customized roles to control each feature authorization as well.
For details on how to create role see document here.
-Thanks
Vinod
