User privileges to execute commands and access data elements on the router are usually specified using certain command rules
and data rules that are created and applied on the user groups.
When the internal process for AAA starts or when you create the first user, the system creates the following set of predefined
groups, command rules and data rules in System Admin VM. These configurations are prepopulated to allow users of different
groups (such as root-system, admin-r and aaa-r) in System Admin VM
You can use the show running-configuration aaa command to view the AAA configurations.
The admin CLI for the user works based on the above configurations. The root-system is the group with the highest privilege
in System Admin VM. The admin-r group has only read and execute access to all data. The aaa-r group has access only to AAA
data. With the introduction of the admin access feature for all users, the NETCONF and gRPC applications can also access the
admin data based on the above rules and groups.
A user profile mapping is an authentication mechanism that
- establishes a direct relationship between user profiles in XR VM and System Admin VM,
- assigns user privileges based on predefined command and data rules for different user groups, and
- streamlines authentication and access control on the system.
User privileges to execute commands and access data elements on the router are defined and enforced by command and data rules
assigned to user groups. When the AAA (Authentication, Authorization, and Accounting) process starts, or when you create the
first user, the system automatically creates and populates a set of predefined groups, command rules, and data rules in the
System Admin VM. These default group assignments, such as root-system, admin-r, and aaa-r, are designed to provide appropriate
privilege levels to users in System Admin VM.
You can use the show running-configuration aaa command to view the AAA configurations and verify current group and rule assignments.
Example configuration
aaa authentication groups group aaa-r gid 100 users %%__system_user__%%
!
aaa authentication groups group admin-r gid 100 users %%__system_user__%%
!
aaa authentication groups group root-system gid 100 users "%%__system_user__%% "
!
aaa authorization cmdrules cmdrule 1 context * command * group root-system ops rx action
accept
!
aaa authorization cmdrules cmdrule 2 context * command "show running-config aaa" group aaa-r
ops rx action accept
!
aaa authorization cmdrules cmdrule 3 context * command "show tech-support aaa" group aaa-r
ops rx action accept
!
aaa authorization cmdrules cmdrule 4 context * command "show aaa" group aaa-r ops rx
action accept
!
aaa authorization cmdrules cmdrule 5 context * command show group admin-r ops rx action
accept
!
aaa authorization datarules datarule 1 namespace * context * keypath * group root-system
ops rwx action accept
!
aaa authorization datarules datarule 2 namespace * context * keypath /aaa group aaa-r ops
r action accept
!
aaa authorization datarules datarule 3 namespace * context * keypath /aaa group admin-r ops
rwx action reject
!
aaa authorization datarules datarule 4 namespace * context * keypath / group admin-r ops r
action accept
These key points summarize how user profile mappings and group rules affect system access and privileges: