EasyManua.ls Logo

Alcatel-Lucent AOS-W 6.5.3.x - Enabling Optional Captive Portal Configurations

Alcatel-Lucent AOS-W 6.5.3.x
1160 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Parameter Description
User idle timeout
The user idle timeout value for this profile. Specify the idle timeout value for the client
in seconds. Valid range is 30-15300 in multiples of 30 seconds. Enabling this option
overrides the global settings configured in the AAA timers. If this is disabled, the
global settings are used.
Redirect URL URL to which an authenticated user will be directed. This parameter must be an abso-
lute URL that begins with either http:// or https://.
URL Hash Key If a redirection URL is defined, enter a URLHash Key to hash the redirect URL using
the specified key.
This parameter enhances security for the Clearpass Guest login URL so that Clear-
pass can trust and ensure that the client MAC address in the redirect URL has not
been tampered with by anyone. Default: Disabled.
Enabling Optional Captive Portal Configurations
The following are optional captive portal configurations:
n Uploading Captive Portal Pages by SSID Association on page 324
n Changing the Protocol to HTTP on page 325
n Configuring Redirection to a Proxy Server on page 326
n Redirecting Clients on Different VLANs on page 327
n Web Client Configuration with Proxy Script on page 327
Uploading Captive Portal Pages by SSID Association
You can upload custom login pages for captive portal into the switch through the WebUI (refer to Creating and
Installing an Internal Captive Portal on page 330). The SSID to which the client associates determines the
captive portal login page displayed.
You specify the captive portal login page in the captive portal authentication profile, along with other
configurable parameters. The initial user role configuration must include the applicable captive portal
authentication profile instance. (In the case of captive portal in the base operating system, the initial user role is
automatically created when you create the captive portal authentication profile instance.) You then specify the
initial user role for captive portal in the AAA profile for the WLAN.
When you have multiple captive portal login pages loaded in the switch, you must configure a unique initial
user role and user role, and captive portal authentication profile, AAA profile, SSID profile, and virtual AP profile
for each WLAN that will use captive portal. For example, if you want to have different captive portal login pages
for the engineering, business and faculty departments, you need to create and configure according to Table 78.
AOS-W 6.5.3.x | User Guide Captive Portal Authentication | 324

Table of Contents