Configuring The Local Portal Server; Customizing Authentication Pages - HP 3600 v2 Series Security Configuration Manual

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; otherwise, the default authentication pages will be used during the
authentication process.

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 will use the default authentication pages for the undefined ones.
For the local portal server to operate normally and steadily, 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
Logon page
Logon success page
Logon failure page
Online page
Pushed after the user gets online for online notification
System busy page
Pushed when the system is busy or the user is in the
logon process
Logoff success page
NOTE:
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 local portal server 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 Logon.htm includes contents that perform Get action on file ca.htm, file ca.htm
cannot include any reference to file Logon.htm.
File name
logon.htm
logonSuccess.htm
logonFail.htm
online.htm
busy.htm
logoffSuccess.htm
138