WO2016082366A1 - Template based logged in user management method, user login method and device - Google Patents

Abstract

Provided are a template based logged in user management method, user login method and device, the template based logged in user management method comprising: configuring one type or more types of authentication, authorization, accounting (AAA) policies; creating an AAA template, bonding the AAA policy to the AAA template; creating a user module of the logged in user; bonding the AAA template to the user module, and solving the problem that users having a same or different login types use a same or different scene of the AAA policy. The method in the present invention flexibly uses the AAA policy, thus enabling more flexible and more convenient login user management of the scene.

Description

Method for managing login user based on template, method and device for user login Technical field

The present invention relates to the field of communications technologies, and in particular, to a method for managing a login user based on a template, and a method and device for logging in to a user.

Background technique

In the existing carrier-class equipment, it is often necessary to log in to the device for configuration of various services. The login type is generally TELNET (a program for remote login on the Internet), and SSH (Secure Shell, a secure shell protocol). , WEB, etc., after user authentication is authenticated, the device can be configured. Generally, the management for login users is mainly AAA, namely Authentication, Authorization, and Accounting.

The authentication method is to verify whether the user accessing the device is legal to determine whether to allow the user to access; the authorization method is to authorize the accessed user to allow those services or what permissions; the accounting method is to record the user operating the device. Usually the three are used together.

A common implementation of AAA is to deploy the AAA method based on the login type or user type. After the AAA is configured, the login type (such as serial port login, TELNET login, SSH login, WEB login, etc.) or user type (login user, ppp user, etc.) The global effect, which objectively limits the user's final AAA method is subject to the login type or user type bound by the AAA method. Take the login type as an example. If the AAA method is bound to line vty 1, the users logging in from vty 1 all correspond to the same AAA method. If you want the same user to adopt the same AAA method when logging in through different vty (virtual teletype terminal), or different users adopt different AAA methods when logging in through the same vty, such deployment is not flexible enough. Similarly, the same situation exists when different AAA methods are deployed for the same user type.

Summary of the invention

In order to solve the above technical problem, an embodiment of the present invention provides a method and a device for managing a login user based on a template, and setting different AAA policies for different AAA templates, and binding the AAA template to a specific user, in order to achieve Different AAA policies for users.

According to an aspect of the present invention, a method for managing a login user based on a template is provided, the method comprising: configuring one or more AAA policies; creating an AAA template, and binding the AAA policy to the AAA template Creating a user mode of the logged in user; and binding the AAA template to the user mode.

Optionally, the AAA template includes one or more of an AAA authentication template, an AAA authorization template, and an AAA accounting template.

Optionally, the AAA policy includes at least: an AAA server type in the AAA server group and an AAA server switching policy in the AAA server group.

Optionally, the method further includes: binding the corresponding login type in the user mode.

Optionally, the user mode includes: a default user mode and a user configuration mode.

Optionally, the login type is: a console login type, a Telnet login type, an SSH login type, an FTP login type, or a WEB login type.

According to another aspect of the present invention, a method for user login is provided, the method includes: acquiring login information and a login type input by a login user; and matching, according to the login information input by the user, whether the device is configured locally. User configuration mode; if it matches, the configured login type is obtained from the matching user configuration mode; otherwise, the configured login type is obtained from the default user mode; the login type of the login user is matched with the configured login type, if If the matching is performed, the AAA template corresponding to the matched user configuration mode or the default user mode is obtained according to the corresponding relationship between the user mode and the AAA template. The AAA template or the AAA authentication and the AAA authorization are initiated according to the matched AAA template.

Optionally, if the login type of the login user does not match the login type corresponding to the user configuration mode, the login failure is prompted.

Optionally, the method further includes: configuring one or more AAA policies; creating an AAA template, binding the AAA policy to the AAA template; creating a user mode of the logged in user; and tying the AAA template Set to the user mode.

According to another aspect of the present invention, there is also provided an apparatus for managing a login user based on a template, the apparatus comprising: a configuration module configured to configure one or more AAA policies; and a first binding module configured to create an AAA a template, the AAA policy is bound to the AAA template; a module is created to create a user mode; and a second binding module is configured to bind the AAA template to the user mode.

Optionally, the device further includes: a third binding module, configured to bind the corresponding login type in the user mode.

According to another aspect of the present invention, there is also provided a device for user login, the device comprising: a first obtaining module, configured to acquire login information and a login type input by a login user; and a first matching module configured to be The login information input by the user matches whether the corresponding user configuration mode is configured locally; if it matches, the configured login type is obtained from the matched user configuration mode; otherwise, the configured login type is obtained from the default user mode; The matching module is configured to match the login type of the login user with the configured login type, and if matched, obtain a matching user configuration mode or a default user mode according to a preset correspondence between the user mode and the AAA template. Corresponding AAA template; the processing module is configured to initiate AAA authentication or AAA authentication and AAA authorization according to the matched AAA template.

Optionally, the device further includes: a prompting module, configured to prompt that the login fails if the login type of the login user does not match the login type corresponding to the user configuration mode.

Optionally, the device further includes: a configuration module, configured to configure one or more AAA policies;

a first binding module, configured to create an AAA template, bind the AAA policy to the AAA template, create a module, and set a user mode, and a second binding module, configured to bind the AAA template Set to the user mode.

The AAA policy can be flexibly used by the method of the present invention to make the login user management of the scenario more flexible and convenient, by using the same or different AAA policies in the scenario of the same or different login types.

DRAWINGS

1 is a flowchart of a method for managing a login user based on a template in an embodiment of the present invention;

2 is a second flowchart of a method for managing a login user based on a template according to an embodiment of the present invention;

3 is a configuration binding relationship between an AAA template and a local user or a default user mode according to an embodiment of the present invention;

4 is a flowchart of TACACS server authentication and authorization in an embodiment of the present invention;

5 is a flowchart of a RADIUS server authentication and authorization in an embodiment of the present invention;

6 is a flow chart of TACACSS server accounting in an embodiment of the present invention;

FIG. 7 is a flowchart of a user login in an embodiment of the present invention; FIG.

FIG. 8 is a second flowchart of user login in an embodiment of the present invention; FIG.

FIG. 9 is a flowchart of interaction between a terminal device, a router, and an AAA server according to an embodiment of the present invention;

10 is a schematic structural diagram of an apparatus for managing a login user based on a template according to the present invention;

FIG. 11 is a schematic structural diagram of an apparatus for logging in by a user in an embodiment of the present invention.

detailed description

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While the embodiments of the present invention have been shown in the drawings, the embodiments Rather, these embodiments are provided so that this disclosure will be more fully understood and the scope of the disclosure will be fully disclosed.

FIG. 1 is a flowchart of a method for managing a login user based on a template according to an embodiment of the present invention, and the specific steps are as follows:

Step S101: Configure one or more AAA policies.

Optionally, the AAA policy includes at least: an AAA server type in the AAA server group and an AAA server switching policy in the AAA server group.

Currently, the common servers are TACACS (Terminal Access Controller Access Control System), RADIUS (Remote User Dial-Up Authentication System), and Diameter (RADIUS Upgrade Protocol). These three are used as examples to describe the configuration policy of the AAA template.

Under the AAA authentication policy, the AAA server type can specify none, TACACS, RADIUS, Diameter, local, or a combination of these types to determine the policy of server switching. Configure the corresponding server switching policy for the TACACS, RADIUS, and Diameter server groups. When an AAA server fails, perform intra-group switching.

Under the AAA authorization policy, the AAA server type can specify none, TACACS, RADIUS, local, or a combination of these types to determine the policy of server switching. Configure the corresponding server switching policy for the TACACS and RADIUS server groups. If an AAA server fails, perform intra-group switching.

Under the AAA accounting policy, the AAA server type can specify none, TACACS, RADIUS, local, or a combination of these types to determine the policy for server switching. Configure the corresponding server switching policy for TACACS and RADIUS server, and perform intra-group switching when a server fails.

Step S103: Create an AAA template, and bind the AAA policy to the AAA template.

In an embodiment of the present invention, the AAA template includes: an AAA authentication template, an AAA authorization template, and an AAA accounting template, wherein each AAA template can be bound with the same or different AAA policies, that is, can be configured in the AAA template. Bind this AAA template to the specified login user, such as the server type, server switching policy, and server group policy. When the user logs in, the AAA template bound to the user is searched to determine a specific AAA policy.

Step S105: Create a user mode of the login user.

That is, user information (user name and password) of the logged-in user is configured, and a user mode corresponding to the logged-in user is generated based on the user information. Optionally, in the embodiment of the present invention, the user mode includes: a default user mode and a user configuration mode. When the user information is configured on the server side, the login user is not created on the local device, and the AAA template is specified as the server authentication. The embodiment of the present invention provides a default user mode, and the AAA template is bound to the default user mode. When the logged in user does not match the local created user, the AAA template bound in the default user mode corresponds to the AAA policy.

Step S107: Bind the AAA template to the user mode.

After the AAA template is configured, the test user is bound to the user configuration. You can use the test user to log in to the AAA template.

In an embodiment of the present invention, an AAA template may be bound to a user mode according to a specific situation, for example:

If the user is not bound to the AAA authentication template or the AAA authentication template is incorrectly configured, the user should explicitly prompt the user that the authentication configuration information is missing or error.

Case 2: In the scenario where the device has a default authorization policy, the user configuration may not be bound to the AAA authorization template. After the user authentication is passed, the default authorization policy is used to grant the user permission. When the AAA authorization server is abnormal or the network is abnormal, the server cannot be obtained. The authorization result on the side, and the default authorization is also used at this time. If there is no default authorization policy and the user is not bound to the AAA authorization template or the AAA authorization template is incorrectly configured, the user should explicitly prompt the user that the authorized configuration information is missing or incorrect in the environment with terminal output, and the user is not allowed to log in.

Case 3: Since the AAA accounting policy is not a mandatory function for the logged-in user, if the AAA accounting function is closed, the user is bound with the AAA accounting template, or when the accounting function is enabled, the user is bound. The billing template is used, but when the template is empty, no billing is performed.

As shown in FIG. 2, a flowchart of the method for managing a login user based on a template in the embodiment of the present invention is different from the method shown in FIG. 1. In FIG. 2, after step S107, the method is Also includes:

Step S109: Bind the corresponding login type in the user configuration mode.

When you need to limit the login type of a certain type of user, you can bind the login type through a certain configuration under the specified user or the default user mode. Any login type is supported by default when the user does not bind the login type.

Compared with common user login management, embodiments of the present invention can customize a very flexible combination of authentication, authorization, and accounting for specific users and specific login types to meet the actual user login scenario and user customized management. .

As shown in FIG. 3, the binding relationship between the AAA template and the user information described in the embodiment of the present invention is as follows:

Step S301: Configure a server group policy, and specify a server group switching policy.

The server group policy includes: a TACACS group T1 policy, a RADIUS group T2 policy, and a Diameter group T3 policy.

Step S303: Create an AAA authentication template X1, bind the server group policy to the AAA authentication template X1, create an AAA authorization template X2, bind the server group policy to the AAA authorization template X2, and create an AAA accounting template X3. Bind the server group policy to the AAA accounting template X3.

Step S305: Create a user Y, and bind the AAA authentication template X1 and the authorization template X2 to Y or bind the AAA authentication template X1, the AAA authorization template X2, and the AAA accounting template X3 to Y.

Step S307: Binding the login type, wherein the login type includes: console, TELNET, SSH, FTP, and WEB.

At this point, the association between the AAA server configuration information, the AAA authentication template, the AAA authorization template, and the user configuration information is established.

The actual configuration information of the present invention is as follows:

As shown in FIG. 4, it is a flowchart of the TACACS server authentication and authorization in the embodiment of the present invention. The scenario in which the user is deployed on the TACACS server side to perform TACACS server authentication and authorization is as follows:

Step S401: Configure two TACACS servers and apply them to the group policy named T1 in TACACS.

Specifically, the code of step S401 is as follows:

Step S403: Create an AAA authentication template 2001, configure the authentication type as TACACS, and bind the TACACS group policy to the AAA authentication template 2001.

Specifically, the code of step S403 is as follows:

Step S405: Create an AAA authorization template 2001, configure the authorization type as TACACS, and bind the TACACS group policy to the AAA authorization template 2001.

Specifically, the code of step S405 is as follows:

Step S407: Create user user1, configure its password as test (in the example, the ciphertext corresponding to test), and bind the AAA authentication template and AAA authorization template created in steps S403 and S405 to user1.

Specifically, the code of step S407 is as follows:

Step S409: If the user is created on the server side and there is no user configuration in the local area, and the server is used for authentication, authorization, and accounting, the AAA authentication template and the AAA authorization template created in steps S403 and S405 are bound in the default user mode.

Specifically, the code of step S409 is as follows:

Step S411: Log in to the device by using the deployed user through the access terminal.

As shown in FIG. 5, it is a flowchart of the RADIUS server authentication and authorization in the embodiment of the present invention. The scenario in which the user is deployed on the RADIUS server side to perform RADIUS server authentication and authorization is as follows:

Step S501: Configure two RADIUS servers and apply them to the group policy whose RADIUS name is R1.

Specifically, the code of step S501 is as follows:

Step S503: Create an AAA authentication template 2002, configure the authentication type to be RADIUS, and bind the RADIUS group policy to the AAA authentication template 2002.

Specifically, the code of step S503 is as follows:

Step S505: Create an AAA authorization template 2002, configure the authorization type to be RADIUS, and bind the RADIUS group policy to the AAA authorization template 2002.

Specifically, the code of step S505 is as follows:

Step S507: Create user user1, configure its password as test, and bind the AAA authentication template and AAA authorization template created in steps S503 and S505 to user1.

Specifically, the code of step S507 is as follows:

Step S509: If the user is created on the server side and there is no user configuration in the local area, and the server is used for authentication, authorization, and accounting, the AAA authentication template and the AAA authorization template created in steps S503 and S505 are bound in the default user mode.

Specifically, the code of step S509 is as follows:

Step S511: Log in to the device by using the deployed user through the access terminal.

The Diameter server is mainly used for user authentication, and is similar to the binding policy of the TACACS authentication template.

As shown in FIG. 6 , the flow chart of the TACACSS server accounting in the embodiment of the present invention is not required for the logged in user. The AAA authentication and authorization functions are slightly different from the AAA authentication and authorization functions. The enable switch is turned off by default. Take the TACACS server accounting function as an example. The specific configuration is as follows:

Step S601: Create an AAA accounting template 2003, configure the accounting type as TACACS, and bind the TACACS group policy to the AAA accounting template 2003. Specifically, the code of step S601 is as follows:

In step S603, the accounting function is enabled in the user1 configuration mode, and the AAA accounting template 2003 created in step S601 is bound to user1:

Specifically, the code of step S603 is as follows:

Step S605: If the user is created on the server side and there is no local user configuration, the accounting function is enabled in the default user mode, as follows:

Specifically, the code of step S605 is as follows:

At this point, all operations after the user logs in will be accounted for in accordance with the AAA Accounting Template 2003 policy. If the accounting function is off (accounting-switch off), the user binds the accounting template of AAA, or when the accounting function is enabled, the user binds the accounting template, but when the template is empty, No accounting is performed.

When you need to limit the login type of the user, you can bind the corresponding login type in the user configuration mode. The common login type is mainly console, TELNET, SSH, FTP, WEB, etc., according to the actual access scenario of the network device. For the different access types, the corresponding command in this example is login-type to restrict users from allowing Telnet and SSH login as an example:

An example of limiting the login type on the server side when a user is not configured locally is as follows:

After the configuration of the scenario described above is complete, you can log in to the device through the specified user.

As shown in FIG. 7 , it is one of flowcharts of user login in the embodiment of the present invention, and the specific steps are as follows:

Step S701: Acquire login information and login type input by the login user.

Step S703: According to the login information input by the user, whether the corresponding user configuration mode is configured locally; if the matching is performed, the configured login type is obtained from the matched user configuration mode; otherwise, the configuration is obtained from the default user mode. Login type;

Step S705: Matching the login type of the login user with the configured login type, and if they match, obtaining a corresponding user configuration mode or a default user mode according to a preset correspondence between the user mode and the AAA template. AAA template;

Step S707: Initiate AAA authentication or AAA authentication and AAA authorization according to the matched AAA template.

In the embodiment of the present invention, if the login type of the login user does not match the login type corresponding to the user configuration mode, the login failure is prompted.

In the embodiment of the present invention, the correspondence between the preset user mode and the AAA template may be established by first configuring one or more AAA policies; then creating an AAA template, and binding the AAA policy to the Under the AAA template; then, create a user mode of the login user; finally bind the AAA template to the user mode.

As shown in FIG. 8 , in the flowchart of the user login in the embodiment of the present invention, the user login process is as follows:

Step S801: Acquire a username and password of the login user.

Step S803: According to the user name and password input by the user, whether the corresponding user mode is configured in the user list local to the device. If it matches, the process goes to step S807; otherwise, the process goes to step S805.

Step S805: Obtain a login type from the default user mode.

Step S807, obtaining a login type of the local configuration user mode;

Step S809: If the login type of the login user matches the configured login type, proceed to step S811; otherwise, a corresponding error prompt is given.

Step S811: Obtain a corresponding AAA method (authentication, authorization, accounting) from the matching user or the default user mode.

Step S813: Initiating an authentication, authorization request specifying the AAA method and waiting for a response from the device or the server. If the authentication and authorization are successful, the user logs in successfully.

The actual interaction process between the terminal device side, the device (telecom scale switch, router) side and the AAA server side is as shown in Figure 9 when the authentication and authorization template of the template number is 2001. As shown in the example of the router, the router prompts the terminal device to input the user name and password. When the terminal device inputs "user1" (user name) and "test" (password), the router performs AAA policy matching according to the user name and password. Then, based on the AAA policy obtained by the router matching, a request for authentication and authorization processing is sent to the AAA server. After the authentication and authorization are successful, the router allows the terminal device to log in.

As shown in FIG. 10, it is a schematic structural diagram of an apparatus for managing a login user based on a template according to the present invention. The apparatus includes: a configuration module 1001, a first binding module 1003, a creating module 1005, and a second binding module 1007, wherein

The configuration module 1001 is configured to configure one or more AAA policies; currently, the common servers are TACACS (Terminal Access Controller Access Control System), RADIUS (Remote User Dial-Up Authentication System), and Diameter (RADIUS Upgrade Protocol). Take these three examples as an example to describe the configuration policy of the AAA template. Under the AAA authentication policy, the AAA server type can specify none, TACACS, RADIUS, Diameter, local, or a combination of these types to determine the policy of server switching. Configure the corresponding server switching policy for the TACACS, RADIUS, and Diameter server groups. When an AAA server fails, perform intra-group switching. Under the AAA authorization policy, the AAA server type can specify none, TACACS, RADIUS, local, or a combination of these types to determine the policy of server switching. Configure the corresponding server switching policy for the TACACS and RADIUS server groups. If an AAA server fails, perform intra-group switching. Under the AAA accounting policy, the AAA server type can specify none, TACACS, RADIUS, local, or a combination of these types to determine the policy for server switching. Configure the corresponding server switching policy for TACACS and RADIUS server, and perform intra-group switching when a server fails.

The first binding module 1003 is configured to create an AAA template, and bind the AAA policy to the AAA template. In an embodiment of the present invention, the AAA template includes: an AAA authentication template, an AAA authorization template, and an AAA accounting template, wherein each AAA template can be bound with the same or different AAA policies, that is, can be configured in the AAA template. Server type, server switching policy, server group policy, etc., in the specified login The user binds this AAA template. When the user logs in, the AAA template bound to the user is searched to determine a specific AAA policy.

The creating module 1005 is configured to create a user mode; that is, configuring user information (user name and password) of the logged-in user, and generating a user mode corresponding to the logged-in user based on the user information. Optionally, in the embodiment of the present invention, the user mode includes: a default user mode and a user configuration mode. When the user information is configured on the server side, the login user is not created on the local device, and the AAA template is specified as the server authentication. The embodiment of the present invention provides a default user mode, and the AAA template is bound to the default user mode. When the logged in user does not match the locally created user, the AAA default method corresponding to the binding in the default user mode is adopted.

The second binding module 1007 is configured to bind the AAA template to the user mode.

Compared with common user login management, embodiments of the present invention can customize a very flexible combination of authentication, authorization, and accounting for specific users and specific login types to meet the actual user login scenario and user customized management. .

Optionally, in another embodiment of the present invention, the apparatus further includes: a third binding module, configured to bind the corresponding login type in the user mode. When you need to limit the login type of a certain type of user, you can bind the login type through a certain configuration under the specified user or the default user mode. Any login type is supported by default when the user does not bind the login type.

FIG. 11 is a schematic structural diagram of an apparatus for logging in by a user in an embodiment of the present invention, where the apparatus includes:

The first obtaining module 1101 is configured to obtain login information input by the login user.

The first matching module 1103 is configured to: according to the login information input by the user, whether the corresponding user configuration mode is configured locally; if the matching is performed, the configured login type is obtained from the matched user configuration mode; otherwise, the default is obtained from the default Get the configured login type in user mode;

The second matching module 1105 is configured to match the login type of the login user with the configured login type, and if matched, obtain a matching user configuration mode according to a preset correspondence between the user mode and the AAA template. The AAA template corresponding to the default user mode;

The processing module 1107 is configured to initiate AAA authentication or AAA authentication and AAA authorization according to the matched AAA template.

Optionally, the device further includes: a prompting module, configured to prompt that the login fails if the login type of the login user does not match the login type corresponding to the user configuration mode.

Optionally, the device further includes:

The configuration module is configured to configure one or more AAA policies;

a first binding module, configured to create an AAA template, and bind the AAA policy to the AAA template;

Create a module set to create a user mode;

The second binding module is configured to bind the AAA template to the user mode.

The above is a preferred embodiment of the present invention, and it should be noted that those skilled in the art can also make several improvements and retouchings without departing from the principles of the present invention. It should also be considered as the scope of protection of the present invention.

Industrial applicability

As described above, with the above-mentioned embodiments and the preferred embodiments, the scenario in which the users of the same or different login types use the same or different AAA policies is solved, and the AAA policy can be flexibly used to enable the login of the scenario. User management is more flexible and convenient.

Claims (14)

A template-based method for managing login users, the method comprising: Configure one or more AAA policies; Create an AAA template, and bind the AAA policy to the AAA template. Create a user mode for the logged in user; Binding the AAA template to the user mode. The method of claim 1, wherein the AAA template comprises one or more of an AAA authentication template, an AAA authorization template, and an AAA accounting template. The method of claim 1, wherein the AAA policy comprises at least: an AAA server type in the AAA server group and an AAA server switching policy in the AAA server group. The method of claim 1 wherein the method further comprises: binding the corresponding login type in the user mode. The method of claim 4 wherein said user mode comprises: a default user mode and a user configuration mode. The method of claim 5, wherein the login type is: a console login type, a TELNET login type, an SSH login type, an FTP login type, or a WEB login type. A method for user login, the method comprising: Obtain login information and login type entered by the login user; According to the login information input by the user, whether the corresponding user configuration mode is configured locally; if yes, the configured login type is obtained from the matched user configuration mode; otherwise, the configured login type is obtained from the default user mode; The AAA template corresponding to the matched user configuration mode or the default user mode is obtained according to the mapping between the preset user mode and the AAA template. AAA authentication or AAA authentication and AAA authorization are initiated according to the matched AAA template. The method of claim 7, wherein if the login type of the login user does not match the login type corresponding to the user configuration mode, the login failure is prompted. The method of claim 7 wherein said method further comprises: Configure one or more AAA policies; Create an AAA template, and bind the AAA policy to the AAA template. Create a user mode for the logged in user; Binding the AAA template to the user mode. A device for managing a login user based on a template, the device comprising: The configuration module is configured to configure one or more AAA policies; a first binding module, configured to create an AAA template, and bind the AAA policy to the AAA template; Create a module set to create a user mode; The second binding module is configured to bind the AAA template to the user mode. The device of claim 10, wherein the device further comprises: The third binding module is configured to bind the corresponding login type in the user mode. A device for user login, the device comprising: The first obtaining module is configured to obtain login information and a login type input by the login user; The first matching module is configured to: according to the login information input by the user, whether the corresponding user configuration mode is configured locally; if yes, obtain the configured login type from the matched user configuration mode; otherwise, from the default user mode Get the configured login type; The second matching module is configured to match the login type of the login user with the configured login type, and if matched, obtain a matching user configuration mode or default according to a preset correspondence between the user mode and the AAA template. User mode corresponding AAA template; The processing module is configured to initiate AAA authentication or AAA authentication and AAA authorization according to the matched AAA template. The device according to claim 12, wherein the device further comprises: a prompting module, configured to prompt the login failure if the login type of the login user does not match the login type corresponding to the user configuration mode. The device of claim 12, wherein the device further comprises: The configuration module is configured to configure one or more AAA policies; a first binding module, configured to create an AAA template, and bind the AAA policy to the AAA template; Create a module, set to create a user mode; The second binding module is configured to bind the AAA template to the user mode.

Images