Create User Profiles and Assign Privileges

To provide controlled access to the System Admin configurations on the NCS 1002, user profiles are created with assigned privileges. The privileges are specified using command rules and data rules. The authentication, authorization, and accounting (aaa) commands are used in the System Admin Config mode for the creation of users, groups, command rules, and data rules. The aaa commands are also used for changing the disaster-recovery password.

Users are authenticated using username and password. Authenticated users are entitled to execute commands and access data elements based on the command rules and data rules that are created and applied to user groups. All users, who are part of a user group, have such access privileges to the system as defined in the command rules and data rules for that user group.

Use the show run aaa command in the System Admin Config mode to view existing aaa configurations.

The topics covered in this chapter are:

Create a User Profile

Create new users for the System Admin. Users are included in a user group and assigned certain privileges. The users have restricted access to the commands and configurations in the System Admin console, based on assigned privileges.

The NCS 1002 supports a maximum of 1024 user profiles.


Note

Users created in the System Admin are different from the ones created in XR. As a result, the username and password of a System Admin user cannot be used to access the XR, and vice versa.


Note

When the user profile is initially created in IOS XR, the user name and password are synchronized with the System Admin if the user does not exist in System Admin. However, when the password is subsequently changed or when the user is removed in XR, the changes are not synchronized with the System Admin. Hence, the user must be created again on the System Admin.

The XR user can access the System Admin by entering admin command in the XR EXEC mode. The NCS 1002 does not prompt you to enter any username and password. The XR user is provided full access to the System Admin console.

Procedure

Step 1

admin

Example:

RP/0/RP0/CPU0:ios# admin

Enters System Admin EXEC mode.

Step 2

configure

Example:

sysadmin-vm:0_RP0# configure

Enters System Admin Config mode.

Step 3

aaa authentication users user user_name

Example:

sysadmin-vm:0_RP0#(config)#aaa authentication users user us1

Creates a new user and enters user configuration mode. In the example, the user "us1" is created.

Step 4

password password

Example:

sysadmin-vm:0_RP0#(config-user-us1)#password pwd1

Enter the password that will be used for user authentication at the time of login into System Admin.

Step 5

uid user_id_value

Example:

sysadmin-vm:0_RP0#(config-user-us1)#uid 100

Specify a numeric value. You can enter any 32 bit integer.

Step 6

gid group_id_value

Example:

sysadmin-vm:0_RP0#(config-user-us1)#gid 50

Specify a numeric value. You can enter any 32 bit integer.

Step 7

ssh_keydir ssh_keydir

Example:

sysadmin-vm:0_RP0#(config-user-us1)#ssh_keydir dir1

Specify any alphanumeric value.

Step 8

homedir homedir

Example:

sysadmin-vm:0_RP0#(config-user-us1)#homedir dir2

Specify any alphanumeric value.

Step 9

Use the commit or end command.

commit-Saves the configuration changes and remains within the configuration session.

end-Prompts user to take one of these actions:

  • Yes-Saves configuration changes and exits the configuration session.

  • No-Exits the configuration session without committing the configuration changes.

  • Cancel-Remains in the configuration session, without committing the configuration changes.

What to do next

Create a User Group

Create a new user group to associate command rules and data rules with it. The command rules and data rules are enforced on all users that are part of the user group.

The NCS 1002 supports a maximum of 32 user groups.

Before you begin

Create a user profile. See Create a User Profile.

Procedure

Step 1

admin

Example:

RP/0/RP0/CPU0:ios# admin

Enters System Admin EXEC mode.

Step 2

configure

Example:

sysadmin-vm:0_RP0# configure

Enters System Admin Config mode.

Step 3

aaa authentication groups group group_name

Example:

sysadmin-vm:0_RP0#(config)#aaa authentication groups group gr1

Creates a new user group (if it is not already present) and enters the group configuration mode. In this example, the user group "gr1" is created.

Note

 

By default, the user group "root-system" is created by the system at the time of root user creation. The root user is part of this user group. Users added to this group get root user permissions.

Step 4

users user_name

Example:

sysadmin-vm:0_RP0#(config-group-gr1)#users us1

Specify the name of the user that should be part of the user group.

You can specify multiple user names enclosed withing double quotes. For example, users "user1 user2 ..." .

Step 5

gid group_id_value

Example:

sysadmin-vm:0_RP0#(config-group-gr1)#gid 50

Specify a numeric value. You can enter any 32 bit integer.

Step 6

Use the commit or end command.

commit-Saves the configuration changes and remains within the configuration session.

end-Prompts user to take one of these actions:

  • Yes-Saves configuration changes and exits the configuration session.

  • No-Exits the configuration session without committing the configuration changes.

  • Cancel-Remains in the configuration session, without committing the configuration changes.

What to do next

Create Command Rules

Command rules are rules based on which users of a user group are either permitted or denied the use of certain commands. Command rules are associated to a user group and get applied to all users who are part of the user group.

A command rule is created by specifying whether an operation is permitted, or denied, on a command. This table lists possible operation and permission combinations:
Operation Accept Permission Reject Permission
Read (R) Command is displayed on the CLI when "?" is used. Command is not displayed on the CLI when "?" is used.
Execute (X) Command can be executed from the CLI. Command cannot be executed from the CLI.
Read and execute (RX) Command is visible on the CLI and can be executed. Command is neither visible nor executable from the CLI.

By default, all permissions are set to Reject .

Each command rule is identified by a number associated with it. When multiple command rules are applied to a user group, the command rule with a lower number takes precedence. For example, cmdrule 5 permits read access, while cmdrule10 rejects read access. When both these command rules are applied to the same user group, user in this group gets read access because cmdrule 5 takes precedence.

As an example, the command rule is created to deny read and execute permissions for the "show platform" command.

Before you begin

Create an user group. See Create a User Group.

Procedure

Step 1

admin

Example:

RP/0/RP0/CPU0:ios# admin

Enters System Admin EXEC mode.

Step 2

configure

Example:

sysadmin-vm:0_RP0# configure

Enters System Admin Config mode.

Step 3

aaa authorization cmdrules cmdrule command_rule_number

Example:

sysadmin-vm:0_RP0#(config)#aaa authorization cmdrules cmdrule 1100

Specify a numeric value as the command rule number. You can enter a 32 bit integer.

Important

 
Do no use numbers between 1 to 1000 because they are reserved by Cisco.

This command creates a new command rule (if it is not already present) and enters the command rule configuration mode. In the example, command rule "1100" is created.

Note

 

By default "cmdrule 1" is created by the system when the root-system user is created. This command rule provides "accept" permission to "read" and "execute" operations for all commands. Therefore, the root user has no restrictions imposed on it, unless "cmdrule 1" is modified.

Step 4

command command_name

Example:

sysadmin-vm:0_RP0#(config-cmdrule-1100)#command "show platform"

Specify the command for which permission is to be controlled.

If you enter an asterisk '*' for command , it indicates that the command rule is applicable to all commands.

Step 5

ops {r | x | rx}

Example:

sysadmin-vm:0_RP0#(config-cmdrule-1100)#ops rx

Specify the operation for which permission has to be specified:

  • r — Read

  • x — Execute

  • rx — Read and execute

Step 6

action { accept | accept_log | reject}

Example:

sysadmin-vm:0_RP0#(config-cmdrule-1100)#action reject

Specify whether users are permitted or denied the use of the operation.

  • accept — users are permitted to perform the operation

  • accept_log — users are permitted to perform the operation and every access attempt is logged.

  • reject — users are restricted from performing the operation.

Step 7

group user_group_name

Example:

sysadmin-vm:0_RP0#(config-cmdrule-1100)#group gr1

Specify the user group on which the command rule is applied.

Step 8

context connection_type

Example:

sysadmin-vm:0_RP0#(config-cmdrule-1100)#context *

Specify the type of connection to which this rule applies. The connection type can be netconf (Network Configuration Protocol), cli (Command Line Interface), or xml (Extensible Markup Language ). It is recommended that you enter an asterisk '*'; this indicates that the command rule applies to all connection types.

Step 9

Use the commit or end command.

commit-Saves the configuration changes and remains within the configuration session.

end-Prompts user to take one of these actions:

  • Yes-Saves configuration changes and exits the configuration session.

  • No-Exits the configuration session without committing the configuration changes.

  • Cancel-Remains in the configuration session, without committing the configuration changes.

What to do next

Create data rules. See Create Data Rules.

Create Data Rules

Data rules are rules based on which users of the user group are either permitted, or denied, accessing and modifying configuration data elements. The data rules are associated to a user group. The data rules get applied to all users who are part of the user group.

Each data rule is identified by a number associated to it. When multiple data rules are applied to a user group, the data rule with a lower number takes precedence.

Before you begin

Create an user group. See Create a User Group.

Procedure

Step 1

admin

Example:

RP/0/RP0/CPU0:ios# admin

Enters System Admin EXEC mode.

Step 2

configure

Example:

sysadmin-vm:0_RP0# configure

Enters System Admin Config mode.

Step 3

aaa authorization datarules datarule data_rule_number

Example:

sysadmin-vm:0_RP0#(config)#aaa authorization datarules datarule 1100

Specify a numeric value as the data rule number. You can enter a 32 bit integer.

Important

 
Do no use numbers between 1 to 1000 because they are reserved by Cisco.

This command creates a new data rule (if it is not already present) and enters the data rule configuration mode. In the example, data rule "1100" is created.

Note

 

By default "datarule 1" is created by the system when the root-system user is created. This data rule provides "accept" permission to "read", "write", and "execute" operations for all configuration data. Therefore, the root user has no restrictions imposed on it, unless "datarule 1" is modified.

Step 4

keypath keypath

Example:

sysadmin-vm:0_RP0#(config-datarule-1100)#keypath  /aaa/disaster-recovery

Specify the keypath of the data element. The keypath is an expression defining the location of the data element. If you enter an asterisk '*' for keypath , it indicates that the command rule is applicable to all configuration data.

Step 5

ops operation

Example:

sysadmin-vm:0_RP0#(config-datarule-1100)#ops rw
Specify the operation for which permission has to be specified. Various operations are identified by these letters:

  • c—Create

  • d—Delete

  • u—Update

  • w— Write (a combination of create, update, and delete)

  • r—Read

  • x—Execute

Step 6

action { accept | accept_log | reject}

Example:

sysadmin-vm:0_RP0#(config-datarule-1100)#action reject

Specify whether users are permitted or denied the operation.

  • accept — users are permitted to perform the operation

  • accept_log — users are permitted to perform the operation and every access attempt is logged

  • reject — users are restricted from performing the operation

Step 7

group user_group_name

Example:

sysadmin-vm:0_RP0#(config-datarule-1100)#group gr1

Specify the user group on which the data rule is applied. Multiple group names can also be specified.

Step 8

context connection type

Example:

sysadmin-vm:0_RP0#(config-datarule-1100)#context *

Specify the type of connection to which this rule applies. The connection type can be netconf (Network Configuration Protocol), cli (Command Line Interface), or xml (Extensible Markup Language ). It is recommended that you enter an asterisk '*', which indicates that the command applies to all connection types.

Step 9

namespace namespace

Example:

sysadmin-vm:0_RP0#(config-datarule-1100)#namespace *

Enter asterisk '*' to indicate that the data rule is applicable for all namespace values.

Step 10

Use the commit or end command.

commit-Saves the configuration changes and remains within the configuration session.

end-Prompts user to take one of these actions:

  • Yes-Saves configuration changes and exits the configuration session.

  • No-Exits the configuration session without committing the configuration changes.

  • Cancel-Remains in the configuration session, without committing the configuration changes.

Change Disaster-recovery Username and Password

When you define the root-system username and password initially after starting the NCS 1002, the same username and password gets mapped as the disaster-recovery username and password for the System Admin mode. However, it can be changed.

The disaster-recovery username and password are useful in these scenarios:

  • Access the system when the AAA database, which is the default source for authentication in System Admin, is corrupted.

  • Access the system through the management port, when, for some reason, the System Admin console is not working.

  • Create new users by accessing the System Admin using the disaster-recovery username and password, when the regular username and password is forgotten.


Note

You can configure only one disaster-recovery username and password at a time.

Before you begin

Complete the user creation. For details, see Create a User Profile.

Procedure

Step 1

admin

Example:

RP/0/RP0/CPU0:ios# admin

Enters System Admin EXEC mode.

Step 2

configure

Example:

sysadmin-vm:0_RP0# configure

Enters System Admin Config mode.

Step 3

aaa disaster-recovery username username password password

Example:

sysadmin-vm:0_RP0#(config)#aaa disaster-recovery username us1 password pwd1

Specify the disaster-recovery username and the password. You have to select an existing user as the disaster-recovery user. In the example, 'us1' is selected as the disaster-recovery user and assigned the password as 'pwd1'. The password can be entered as a plain text or md5 digest string.

When you need to make use of the disaster recovery username, you need to enter it as username@localhost .

Step 4

Use the commit or end command.

commit-Saves the configuration changes and remains within the configuration session.

end-Prompts user to take one of these actions:

  • Yes-Saves configuration changes and exits the configuration session.

  • No-Exits the configuration session without committing the configuration changes.

  • Cancel-Remains in the configuration session, without committing the configuration changes.