ProCurve 2900 Manual page 90

Web and MAC Authentication
Setup Procedure for Web/MAC Authentication
3-18
To configure a web server on your network, follow the instructions in the
documentation provided with the server.
This section describes how to use HTML skeleton pages as a basis to create
customized login web pages for web authentication on your ProCurve
switches.
When you customize an HTML skeleton file, follow these guidelines:
■ Store all customized login web pages (including all graphics, and
HTML frames) that you create for client login on each web server at
the page path you configure with the aaa port-access web-based ewa­
server command.
Do not change the name of each HTML file (index.html, accept.html,
■
and so on).
■ Do not change any of the HTML source code that appears in bold in
the skeleton pages in this section.
Insert the prefix /EWA/ before any reference to a graphic, HTML frame,
■
or HTML file; for example, /EWA/loginprocess and /EWA/index.html.
HTML skeleton pages use Embedded Switch Includes (ESIs) or Active
■
Server Pages. ESIs behave as follows:
i. A client's web browser sends a request for an HTML file. The switch
passes the request to a configured EWA web server.
ii. The web server responds by sending a customized HTML page to the
switch. Each ESI call in the HTML page is replaced with the value (in
plain text) retrieved by the call.
iii. The switch sends the final version of the HTML page to the client's
web browser.
■ The HTML skeleton pages that you can customize are as follows:
index.html
accept.html
authen.html
reject_unauthvlan.html
statusprocess.html
timout.html
retry_login.html
loginprocess.html
sslredirect.html
rejectnovlan.html