Configuring local users

To implement local AAA, you must create local users and configure user attributes on the device. Local users and attributes are stored on the device in the local user database. Local users are uniquely identified by username. Configurable local user attributes are as follows:

• Service type:

  Services that the user can use. Local authentication checks the service types of a local user. If none of the service types are available, the user cannot pass authentication.

  Service types include FTP, LAN access, Portal, SSH, Telnet, Web, and terminal.

• User state:

  Whether or not a local user can request network services. There are two user states: active and blocked. A user in active state can request network services, but a user in blocked state cannot.

• Maximum number of users using the same local user account:

  Number of users who can use the same local user account for local authentication.

• Validity time and expiration time:

  Validity time and expiration time of a local user account. A user must use a valid local user account to pass local authentication. To meet temporary network access requirements, you can create a guest account and specify a validity time and an expiration time for the account to control the validity of the account.

• User group:

  Each local user belongs to a local user group and bears all attributes of the group, such as the password control attributes and authorization attributes. For more information about local user group, see "Configuring user group attributes."

• Password control attributes:

  Password control attributes help you control the security of local users' passwords. Password control attributes include password aging time, minimum password length, and password composition policy.

  You can configure a password control attribute in system view, user group view, or local user view, making the attribute effective for all local users, all local users in a group, or only the local user. A password control attribute with a smaller effective range has a higher priority. For more information about password management and global password configuration, see "Configuring password control." For more information about password control commands, see Security Command Reference.

• Binding attributes:

  Binding attributes are used for controlling the scope of users. They are checked during local authentication of a user. If the attributes of a user do not match the binding attributes configured for the local user account, the user cannot pass authentication. Binding attributes include the IP address, access port, MAC address, and native VLAN.

• Authorization attributes:

  Rights a user has after passing local authentication. Authorization attributes include the ACL, idle cut function, user level, user role, user profile, VLAN, and FTP/SFTP work directory. For more information about authorization attributes, see "Configuring local user attributes."

  Every configurable authorization attribute has its definite application environments and purposes. When you configure authorization attributes for a local user, consider which attributes are needed and which are not.

  You can configure an authorization attribute in user group view or local user view to make the attribute effective for all local users in the group or only for the local user. The setting of an authorization attribute in local user view takes precedence over that in user group view.

Follow these guidelines when you configure local user attributes:

• When the password control feature is enabled globally (by using the password-control enable command), local user passwords are not displayed.

• If the user interface authentication mode (set by the authentication-mode command in user interface view) is AAA (scheme), the commands that a login user can use after login depend on the privilege level authorized to the user. If the user interface authentication mode is password (password) or no authentication (none), the commands that a login user can use after login depend on the level configured for the user interface (by using the user privilege level command in user interface view). For an SSH user using public key authentication, available commands depend on the level configured for the user interface. For more information about user interface authentication mode and user interface command level, see Fundamentals Configuration Guide.

• You can configure the user profile authorization attribute in local user view, user group view, and ISP domain view. The setting in local user view has the highest priority, and that in ISP domain view has the lowest priority. For more information about user profiles, see "Configuring a user profile."

• You cannot delete a local user that is the only security log manager in the system, nor can you change or delete the security log manager role of the user. To do so, you must specify a new security log manager first.

To configure the attributes of a local user:

User groups simplify local user configuration and management. A user group comprises a group of local users and has a set of local user attributes. Configure local user attributes for a user group to implement centralized user attributes management for the local users in the group. Configurable user attributes include password control attributes and authorization attributes.

By default, every newly added local user belongs to the default user group system and bears all attributes of the group. To assign a local user to a different user group, use the user-group command in local user view.

To configure attributes for a user group: