Filter
Top Products
l "Redirecting Clients on Different VLANs" on page 253
l "Web Client Configuration with Proxy Script" on page 254
Uploading Captive Portal Pages by SSID Association
You can upload custom login pages for captive portal into the controller through the WebUI (refer to "Creating and
Installing an Internal Captive Portal" on page 256). 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 controller, 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 69.
Entity Engineering Business Faculty
Captive portal login page /auth/eng-login.html /auth/bus-login.html /auth/fac-login.html
Captive portal user role eng-user bus-user fac-user
Captive portal
authentication profile
eng-cp
(Specify /auth/eng-login.html
and eng-user)
bus-cp
(Specify /auth/bus-login.html
and bus-user)
fac-cp
(Specify /auth/bus-login.html
and fac-user)
Initial user role eng-logon
(Specify the eng-cp profile)
bus-logon
(Specify the bus-cp profile)
fac-logon
(Specify the fac-logon
profile)
AAA profile eng-aaa
(Specify the eng-logon user
role)
bus-aaa
(Specify the bus-logon user
role)
fac-aaa
(Specify the fac-logon user
role)
SSID profile eng-ssid bus-ssid fac-ssid
Virtual AP profile eng-vap bus-vap fac-vap
Table 69:
Captive Portal login Pages
Changing the Protocol to HTTP
By default, the HTTPS protocol is used on redirection to the Captive Portal page. If you need to use HTTP instead,
you need to do the following:
l Modify the captive portal authentication profile to enable the HTTP protocol.
l
For captive portal with role-based access only
—Modify the captiveportal policy to permit HTTP traffic instead of
HTTPS traffic.
In the base operating system, the implicit ACL captive-portal-profile is automatically modified.
To change the protocol to HTTP via the WebUI:
DellPowerConnectW-SeriesArubaOS6.2 | User Guide CaptivePortalAuthentication | 251