Web and MAC Authentication

Customizing Web Authentication HTML Files (Optional)

To configure a web server on your network, follow the instructions in the documentation provided with the server.

Before you enable custom Web Authentication pages, you should:

Determine the IP address or host name of the web server(s) that will host your custom pages.

Determine the path on the server(s) where the HTML files (including all graphics) used for the login pages are stored.

Configure and start the web server(s).

Create the customized web pages as described in “Customizing HTML Templates”, and store them in the document path on the designated servers.

Test that they are accessible at the designated URL(s).

Customizing HTML Templates

When you customize an HTML template, follow these guidelines:

Do not change the name of any of the HTML files (index.html, accept.html, and so on).

Some template pages use Embedded Switch Includes (ESIs) or Active Server Pages. These should not be modified when customizing HTML files. 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 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.

Store all customized login web pages (including any graphics) that you create for client login on each web server at the path you will configure with the aaa port-access web-based ewa-server command.

3-35