H3C MSR Series Command Reference Manual page 335

device-type: Specifies an endpoint type.
computer: Specifies the endpoint type as computer.
pad: Specifies the endpoint type as tablet.
phone: Specifies the endpoint type as mobile phone.
device-name device-name: Specify an endpoint by its name, a case-sensitive string of 1 to 127
characters. The specified endpoint name must have been predefined on the device. Otherwise, the
bound authentication page file does not take effect.
ssid ssid-name: Specifies an SSID by its name, a case-insensitive string of 1 to 32 characters. An
SSID string can contain letters, digits, and spaces, but the start and end characters cannot be
spaces. An SSID string cannot be f, fi, fil, or file.
file file-name: Specifies an authentication page file by the file name (without the file storage
directory). A file name is a string of 1 to 91 characters, and can contain letters, digits, and
underscores (_). You must edit the authentication pages, compress them to a .zip file, and then
upload the file to the root directory of the storage medium of the device.
Usage guidelines
This command implements customized authentication page pushing for portal users. After you
configure this command, the device pushes authentication pages to users according to the user
SSID, endpoint name, and endpoint type.
When a Web user triggers local portal authentication, the device searches for a binding that matches
the user's SSID, endpoint name, and endpoint type.
•
If the binding exists, the device pushes the bound authentication pages to the user.
•
If multiple matching binding entries are found, the device selects an entry in the following order:
a. The entry that specifies the SSID, endpoint name, and endpoint type.
b. The entry that specifies the SSID and endpoint name.
c. The entry that specifies the SSID and endpoint type.
d. The entry that specifies only the SSID.
e. The entry that specifies the endpoint name and endpoint type.
f. The entry that specifies only the endpoint name.
g. The entry that specifies only the endpoint type.
•
If the binding does not exist, the device pushes the default authentication pages to the user.
When you configure this command, follow these restrictions and guidelines:
•
If the name or content of the file in a binding entry is changed, you must reconfigure the binding.
•
To reconfigure or modify a binding, simply re-execute this command without canceling the
existing binding.
•
If you execute this command multiple times to bind an SSID, endpoint name, or endpoint type to
different authentication page files, the most recent configuration takes effect.
•
You can configure multiple binding entries on the device.
Examples
# Create a local portal Web server and specify HTTP to exchange information with clients.
<Sysname> system-view
[Sysname] portal local-web-server http
# Bind the SSID SSID1 to the authentication page file file1.zip.
[Sysname-portal-local-websvr-http] logon-page bind ssid SSID1 file file1.zip
# Bind the endpoint type iphone to the authentication page file file2.zip.
[Sysname-portal-local-websvr-http] logon-page bind device-type phone file file2.zip
312