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

Reminder

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

upgrade

S12700 V200R011C10 Configuration Guide - User Access and Authentication

This document describes the working mechanisms, configuration procedures, and configuration examples of User Access and Authentication features, such as AAA, DAA, NAC, PPPoE, Policy Association, and IP session.
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-26.

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

The device has two default domains: default (global default domain for common access users) and default_admin (global default domain for the administrator). The two domains can be modified but not deleted. If the domain of an access user cannot be obtained, the default domain is used.
  • The default domain is used for access users (users who use NAC for authentication). By default, local authentication is performed for users in this domain.
  • The default_admin domain is used for administrators (logging in through HTTP, SSH, Telnet, FTP, or console port). By default, local authentication is performed for users in this domain.
NOTE:

A user-defined domain can be configured as a global default domain for common access users and administrators.

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 scheme including local authentication, local authorization, and non-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.

Translation
Download
Updated: 2019-10-21

Document ID: EDOC1000178117

Views: 118898

Downloads: 55

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