Rules on post request attributes, Rules on file size and contents, Portal authentication configuration example – H3C Technologies H3C WX6000 Series Access Controllers User Manual

Page 411: Network requirements

Advertising
background image

36-15

Get requests allow no recursion. For example, if file Logon.htm includes contents that perform Get

action on file ca.htm, file ca.htm cannot include any reference to file Logon.htm.

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 logon.cgi. Otherwise, user information cannot be sent to the local portal server.

The username attribute is fixed as PtUser, and the password attribute is fixed as PtPwd.

Attribute PtButton is required to indicate the action that the user requests, which can be Logon or

Logoff.

A logon Post request must contain PtUser, PtPwd, and PtButton attributes.

A logoff Post request must contain the PtButton attribute.

2) Authentication

pages

logon.htm and logonFail.htm must contain the logon Post request.

The following example shows part of the script in page logon.htm.

<form action=logon.cgi method = post >

<p>User name:<input type="text" name = "PtUser" style="width:160px;height:22px"

maxlength=64>

<p>Password :<input type="password" name = "PtPwd" style="width:160px;height:22px"

maxlength=32>

<p><input type=SUBMIT value="Logon" name = "PtButton" style="width:60px;">

</form>

3) Authentication

pages

logonSuccess.htm and online.htm must contain the logoff Post request.

The following example shows part of the script in page online.htm.

<form action=logon.cgi method = post >

<p><input type=SUBMIT value="Logoff" name="PtButton" 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.

These zip files can be transferred to the device through FTP or TFTP, and must be saved in the

root directory or the portal directory under the root directory of the device.

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, should be no more than 500 KB.

The size of a single page, including the main authentication page and the page elements, should

be no more than 50 KB before being compressed.

Page elements are files that the authentication pages need to reference, for example, back.jpg on

page Logon.htm. Page elements, such as HTML, JS, CSS, and pictures, can contain only static

contents.

Portal Authentication Configuration Example

Network requirements

As shown in

Figure 36-12

:

Advertising