- Table of Contents
-
- 11-Security Configuration Guide
- 00-Preface
- 01-AAA configuration
- 02-Portal configuration
- 03-User profile configuration
- 04-Password control configuration
- 05-Keychain configuration
- 06-Public key management
- 07-PKI configuration
- 08-IPsec configuration
- 09-Group domain VPN configuration
- 10-SSH configuration
- 11-SSL configuration
- 12-SSL VPN configuration
- 13-ASPF configuration
- 14-APR configuration
- 15-Session management
- 16-Connection limit configuration
- 17-Object group configuration
- 18-Object policy configuration
- 19-Attack detection and prevention configuration
- 20-ARP attack protection configuration
- 21-ND attack defense configuration
- 22-uRPF configuration
- 23-Crypto engine configuration
- 24-FIPS configuration
- 25-SMA configuration
- Related Documents
-
Title | Size | Download |
---|---|---|
03-User profile configuration | 41.44 KB |
Configuring user profiles
Overview
A user profile saves a set of predefined parameters, such as a CAR policy, a QoS policy, or a connection limit policy.
The user profile application allows flexible traffic policing on a per-user basis. Each time a user passes authentication, the device automatically applies the parameters in the user profile to this user.
The user profile restricts authenticated user behavior as follows:
1. After the authentication server verifies a user, the server sends the device the name of the user profile specified for the user.
2. The device applies the parameters in the user profile to the user.
3. When the user logs out, the device automatically removes the user profile parameters.
Configuration restrictions and guidelines
When you configure user profiles, follow these restrictions and guidelines:
· Configure authentication parameters before you create a user profile. The user profile supports working with PPPoE, portal, and IPoE.
· Specify a user profile for each user account:
¡ In remote authentication, specify a user profile on the authentication server.
¡ In local authentication, specify a user profile in the local user view. For information about local users, see "Configuring AAA."
Configuring a user profile
By default, no user profiles exist. You can use the command to enter the view of an existing user profile. |
||
3. (Optional.) Specify a queue for session packets that use the user profile. |
By default, no queue exists for saving session packets for a user profile. Session packets are scheduled based on the scheduling priority that the specified queue has. |
|
4. Apply a QoS policy, CAR policy, GTS policy, or connection limit policy. |
N/A |
For information about QoS policy, CAR, and GTS configuration, see ACL and QoS Configuration Guide. For information about connection limit configuration, see "Configuring connection limits." |
Displaying and maintaining user profiles
Execute display commands in any view.
display user-profile [ name profile-name ] [ slot slot-number ] |
|
display user-profile [ name profile-name ] [ chassis chassis-number slot slot-number ] |