Why is the Captive Portal page not displayed when using Captive Portal 3.1?

Aruba Employee

Product and Software: This article applies to all Aruba controllers and ArubaOS version 3.1.x and later.

 

Often the Captive Portal page will not display when Captive Portal 3.1 is being used. When the customer launches a browser on the client, the error "Web Authentication is Disabled on this server" is displayed. 


Make sure that the role that the client gets after connecting has the Captive Portal profile attached to it. To check that, issue the following command: 

 

show rights <Role Name>

Derived Role = 'logon'
Bandwidth = No Limit
L2TP Pool = default-l2tp-pool
PPTP Pool = default-pptp-pool
Periodic reauthentication: Disabled
ACL Number = 1/0

Captive Portal profile = default <-----Here it should show the Captive Portal profile that is configured.

access-list List
----------------
Position Name Location
-------- ---- --------
1 logon-control
2 captiveportal
3 vpnlogon

 

Add the Captive Portal to the role by issuing the following command: 

 

configure terminal 
user-role <Name of the user-role> 
captive-portal <Name of the profile that the customer wants to apply> 

 

To add the Captive Portal to the role using the GUI, follow these steps:

 

1) Navigate to Configuration > Access Control > System/User Roles (whichever role is being used).

2) Select the role and click Edit.

3) At the bottom of the page, select the Captive Portal profile from the drop-down and click Apply and Save. 


Note: The GUI option is not working in Captive Portal 3.1.0.1 and 3.1.0.3. A blank drop-down box is displayed. Use the CLI to add the Captive Portal to the role.

 

 

 

 

Version history
Revision #:
1 of 1
Last update:
‎07-09-2014 03:34 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.