247
Configuring Web-Based Authentication
Information About Configuring Web-Based Authentication
Any images on the custom pages must be on an accessible HTTP server. Configure an intercept ACL within the
admission rule.
Any external link from a custom page requires configuration of an intercept ACL within the admission rule.
To access a valid DNS server, any name resolution required for external links or images requires configuration of an
intercept ACL within the admission rule.
If the custom web pages feature is enabled, a configured auth-proxy-banner is not used.
If the custom web pages feature is enabled, the redirection URL for successful login feature is not available.
To remove the specification of a custom file, use the no form of the command.
Because the custom login page is a public web form, consider these guidelines for the page:
The login form must accept user entries for the username and password and must show them as uname and pwd.
The custom login page should follow best practices for a web form, such as page timeout, hidden password, and
prevention of redundant submissions.
You can substitute your HTML pages, as shown in Figure 28, for the default internal HTML pages. You can also specify a
URL to which users are redirected after authentication occurs, which replaces the internal Success page.
Figure 28 Customizeable Authentication Page
Web-Based Authentication Interactions with Other Features
Port Security, page 248
LAN Port IP, page 248
Gateway IP, page 248
ACLs, page 248
To Next Page
Loading...
Need help?
General