H3C S5600 Series Operation Manual page 595

Main authentication page
Online page
Pushed for online state notification
System busy page
Pushed when the system is busy or the user is in
the login process
Authentication-free page
logout success page
You can define the names of the files other than the main authentication page files. The file
names and directory names are case-insensitive.
Rules on page requests
The web authentication module supports only Post and Get requests.
Get requests are used to get the static files in the authentication pages and allow no
recursion. For example, if file Login.htm includes contents that perform Get action on
file ca.htm, file ca.htm cannot include any reference to file Login.htm.
Post requests are used when users submit username and password pairs, log on the
system, and log off the system.
Rules on Post request attributes
1) Observe the following requirements when editing a form of an authentication page:
An authentication page can have multiple forms, but there must be one and only one
form whose action is null. Otherwise, user information cannot be sent to the local portal
server.
The username attribute is fixed as WaUser, and the password attribute is fixed as
WaPwd.
Attribute WaButton is required to indicate the action that the user requests, which can
be Login or Logout.
A login Post request must contain WaUser, WaPwd, and WaButton attributes.
A Logout Post request must contain the WaButton attribute.
2) Authentication pages login.htm and loginFail.htm must contain the login Post
request.
The following example shows part of the script in page login.htm.
<form method = post >
<p>User name:<input type="text" name = "WaUser" style="width:160px;height:22px"
maxlength=64>
<p>Password
style="width:160px;height:22px" maxlength=32>
<p><input type=SUBMIT value="Login" name = "WaButton" style="width:60px;">
</form>
:<input type="password"
online.htm
busy.htm
freeUser.htm
logoutSuccess.htm
1-6
File name
name = "WaPwd"