Enabling strict-checking on portal authorization information
The strict checking mode allows a portal user to stay online only when the authorized information for the user is successfully deployed on the interface or service template.
You can enable strict checking on authorized ACLs, authorized user profiles, or both. If you enable both ACL checking and user profile checking, the user will be logged out if either checking fails.
An ACL/user profile checking fails when the authorized ACL/user profile does not exist on the device or the ACL/user profile fails to be deployed.
To enable strict-checking on portal authorization information on an interface:
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter interface view. | interface interface-type interface-number | N/A |
3. Enable strict checking mode on portal authorization information. | portal authorization { acl | user-profile } strict-checking | By default, the strict checking mode is disabled. In this case, the portal users stay online even when the authorized ACLs or user profiles do not exist or fail to be deployed. |
To enable strict-checking on portal authorization information on a service template:
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter service template view. | wlan service-template service-template-name | N/A |
3. Enable strict checking mode on portal authorization information. | portal authorization { acl | user-profile } strict-checking | By default, the strict checking mode is disabled. In this case, the portal users stay online even when the authorized ACLs or user profiles do not exist or fail to be deployed. |