42-3
Software Configuration Guide—Release 15.0(2)SG
OL-23818-01
Chapter 42 Configuring Web-Based Authentication About Web-Based Authentication
For Layer 3 interfaces, web-based authentication sets an HTTP intercept ACL when the feature is
configured on the interface (or when the interface is put in service).
For Layer 2 interfaces, web-based authentication detects IP hosts using the following mechanisms:
ARP-based trigger—ARP redirect ACL allows web-based authentication to detect hosts with static
IP address or dynamically acquired IP address.
Dynamic ARP inspection (DAI)
DHCP snooping—Web-based authentication is notified when the switch creates a DHCP binding
entry for the host.
Session Creation
When web-based authentication detects a new host, it creates a session as follows:
Checks for Auth bypass
If the host IP is not on the exception list, web-based authentication sends a nonresponsive host
(NRH) request to the server.
If the server response is Access Accepted, authorization is bypassed for this host. The session is
established.
Sets up the HTTP Intercept ACL
If the server response to the NRH request is Access Rejected, the HTTP intercept ACL is activated
and the session waits for HTTP traffic from the host.
Authentication Process
When you enable web-based authentication, the following events occur:
The user initiates an HTTP session.
The HTTP traffic is intercepted, and authorization is initiated. The switch sends the login page to
the user. The user enters a username and password on the login page, and the switch sends the entries
to the authentication server.
If the client identity is valid and the authentication succeeds, the switch downloads and activates the
user’s access policy from the authentication server. The login success page is sent to the user.
If the authentication fails, the switch sends the login fail page. The user retries the login. If the
maximum number of attempts fails, the switch sends the login expired page and the host is placed
in a watch list. After the watch list times out, the user can retry the authentication process.
If the authentication server does not respond to the switch, and if an AAA fail policy is configured,
the switch applies the failure access policy to the host. The login success page is sent to the user.
See the “Customization of the Authentication Proxy Web Pages” section on page 42-4.
The switch reauthenticates a client when the host does not respond to an ARP probe on a Layer 2
interface, or the host does not send any traffic within the idle timeout on a Layer 3 interface.
The feature applies the downloaded timeout or the locally configured session timeout.
If the terminate action is RADIUS, the feature sends a nonresponsive host (NRH) request to the
server. The terminate action is included in the response from the server.
If the terminate action is default, the session is dismantled and the applied policy is removed.