Note You should use global parameter-map (for method-type, custom, and redirect) only for using the same web authentication methods like consent, web consent, and webauth, for all the clients and SSIDs. This ensures that all the clients have the same web-authentication method. If the requirement is to use Consent for one SSID and Web-authentication for another SSID, then you should use two named parameter-maps. You should configure Consent in first parameter-map and configure webauth in second parameter-map. Note The traceback that you receive when webauth client tries to do authentication does not have any performance or behavioral impact.
It happens rarely when the context for which FFM replied back to EPM for ACL application is already dequeued (possibly due to timer expiry) and the session becomes ‘unauthorized’. Based on where the web pages are hosted, the local web authention can be categorozied as follows: Internal —The internal default HTML pages (Login, Success, Fail, and Expire) in the controller are used during the local web authentication. Customized —The customized web pages (Login, Success, Fail, and Expire) are downloaded onto the controller and used during the local web authentication. External —The customized web pages are hosted on the external web server instead of using the in-built or custom web pages.
Based on the various web authentication pages, the types of web authentication are as follows: Webauth —This is a basic web authentication. Herein, the controller presents a policy page with the user name and password. You need to enter the correct credentials to access the network. Consent or web-passthrough —Herein, the controller presents a policy page with the Accept or Deny buttons. You need to click the Accept button to access the network. Webconsent —This is a combination of webauth and consent web authentication types. Herein, the controller presents a policy page with Accept or Deny buttons along with user name or password.
You need to enter the correct credentials and click the Accept button to access the network. Device Roles With web-based authentication, the devices in the network have these specific roles: Client —The device (workstation) that requests access to the LAN and the services and responds to requests from the switch. The workstation must be running an HTML browser with Java Script enabled. Authentication server —Authenticates the client. The authentication server validates the identity of the client and notifies the switch that the client is authorized to access the LAN and the switch services or that the client is denied.
Switch —Controls the physical access to the network based on the authentication status of the client. The switch acts as an intermediary (proxy) between the client and the authentication server, requesting identity information from the client, verifying that information with the authentication server, and relaying a response to the client. Web-Based Authentication Device Roles Web-Based Authentication 2