No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Configuration Guide - Security

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

This document describes the configurations of Security, including ACL, local attack defense, MFF, attack defense, traffic suppression and storm control, ARP security, Port security, DHCP snooping, ND snooping, PPPoE+, IPSG, SAVI, separating the management plane from the service plane, security risks.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Domain-based User Management

Domain-based User Management

A domain is a group of users.

A NAS manages users based on domains. Each access user belongs to a domain that is determined by the user name provided for login, as shown in Figure 1-16.

Figure 1-16 Using the user name to determine the domain

Two default domains named default and default_admin are available on a device. They can be modified but not deleted.

The default domain is not used. The default_admin domain is used for administrators (logging in through SSH, Telnet, FTP, or console port). By default, local authentication is performed for administrators in this domain when the administrators log in without entering the domain name.

The preconfigured authentication, authorization, and accounting schemes are used in the corresponding domain view to implement authentication, authorization, and accounting for users. AAA provides the default schemes including local authentication, local authorization, and local accounting. If no authentication, authorization, or accounting scheme is applied to a domain, the default schemes are used for users in this domain.

Authorization information delivered by an AAA server is used preferentially because authorization information configured in a domain has a lower priority. When the AAA server does not have or does not support authorization, the authorization attributes configured in a domain take effect. In this manner, you can increase services flexibly by means of domain management, regardless of the authorization attributes provided by the AAA server.

Updated: 2019-04-20

Document ID: EDOC1100074765

Views: 22885

Downloads: 93

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next