Configuring the local portal server, Rules on file names, Customizing authentication pages – H3C Technologies H3C WX3000E Series Wireless Switches User Manual
Page 172
158
NOTE:
•
The maximum number of portal servers that you can specify on the access device is 32.
•
The specified parameters of a portal server can be modified or deleted only if the portal server is not
referenced on any interface.
•
For local portal server configuration, the keywords key, port, and url are usually not required and, if
configured, do not take effect. When using local portal servers for stateful failover in wireless
environments, however, the keyword url is required and the address format must be
http://
ip-address/portal/logon.htm or https://ip-address/portal/logon.htm. Which address format is
used depends the protocol type (HTTP or HTTPS, configured by the portal local-server command)
supported by the local portal servers. The
ip-address is the virtual IP address of the VRRP group to which
the downlink belongs.
•
When a local portal server is used, the re-DHCP portal authentication mode (redhcp) can be configured
but does not take effect.
Configuring the local portal server
Configuring a local portal server is required only for local portal authentication. During local portal
authentication, the local portal server pushes authentication pages to users. You can define the
authentication pages for users. If you do not define them, the default authentication pages are used
during the authentication process.
In a wireless network, you can bind a Service Set Identifier (SSID) to a set of authentication pages. The
system selects authentication pages for a user in this order: the authentication pages bound with the SSID
of the user, the user-defined default authentication pages, and the system default authentication pages.
Customizing authentication pages
Customized authentication pages exist in the form of HTML files. You can compress them and then save
them in the storage medium of the access device.
A set of authentication pages includes six main authentication pages and their page elements. The six
main authentication pages are the logon page, the logon success page, the logon failure page, the
online page, the system busy page, and the logoff success page. The page elements refer to the files that
the authentication pages reference, for example, back.jpg for page Logon.htm. Each main
authentication page can reference multiple page elements. If you define only some of the main
authentication pages, the system uses the default authentication pages for the undefined ones.
For the local portal server to operate normally and steadily, you must follow the following rules when
customizing authentication pages:
Rules on file names
The main authentication pages have predefined file names, which cannot be changed.
Table 9 Main authentication page file names
Main authentication page File
name
Logon page
logon.htm
Logon success page
logonSuccess.htm
Logon failure page
logonFail.htm