Configuring Web Authentication Transition - H3C S3100 Series Operation Manual

<p><input type=SUBMIT value="Login" name = "WaButton" style="width:60px;">
</form>
3) Authentication pages loginSuccess.htm and online.htm must contain the logout Post request.
The following example shows part of the script in page online.htm.
<form action=login.cgi method = post >
<p><input type=SUBMIT value="Logout" name="WaButton" style="width:60px;">
</form>
Rules on page file compression and saving
A set of authentication page files must be compressed into a standard zip file. A zip file name is in
the form of *****.zip, and can contain only letters, numerals, and underscores.
Zip files can be transferred to the device through FTP or TFTP.
Rules on file size and contents
For the system to push customized authentication pages smoothly, you need comply with the following
size and content requirements on authentication pages.
The size of the zip file of each set of authentication pages, including the main authentication pages
and the page elements, must be no more than 500 KB.
The size of a single page, including the main authentication page and the page elements, must be
no more than 50 KB before being compressed.
Page elements can contain only static contents such as HTML, JS, CSS, and pictures.

Configuring Web Authentication Transition

A WLAN client is connected to a switch through a wireless access point (AP). It may move between the
ports of the switch when it, for example, roams between different APs. If the client moves to another port
after passing web authentication, the switch will reject the access of the client because it cannot sense
the port transition and thus web re-authentication cannot be triggered. To solve this problem, web
authentication transition is introduced. It has the following two transition modes:
auto: In auto mode, a web authenticated user can move between ports in the same access VLAN
without needing re-authentication and the switch keeps the user in authenticated state on the new
port after transition.
secure: In secure mode, a web authenticated user must be re-authenticated before it can access
another port. If the user passes re-authentication, the switch deletes the connection information of
the user on the previous port and creates new connection information for the user on the new
access port. If not, the user cannot access the new port but can still access the previous port.
Follow these steps to configure the transition mode for Web authentication users:
Enter system view
Configure the transition mode for Web
authentication users
To do... Use the command...
system-view
web-authentication move-mode {auto
| secure }
1-8
Remarks
—
Required
secure by default.