Dell PowerConnect W Clearpass 100 Software ArubaOS Integration Cheat Sheet - Page 12

Captive Portal Profile.

Page 12 highlights

ArubaOS + Amigopod Integration Cheet Sheet The IP Address should be set to Aruba Controller IP Address. That is, this address needs to be available from the wireless/wired client via the captiveportal policy on the controller. As you can see there are several Login Form options that allow you to override the default Login Form and Labels used to reference User and Password fields. These typically do not need to be changed. The Pre-­‐Auth Check is only required for Advanced configurations where you might need to ensure the username and password pair is valid before initiating the RADIUS transaction from the Aruba Controller. Given the Web Login and RADIUS database is hosted on the same appliance we can perform a query locally prior to firing a RADIUS transaction. You can enable the display of an Accept Terms & Conditions option of the login page if required. This refers to the default T&Cs URL defined under Guest Manager Customization Customize Guest Manager. Unfortunately, as of ArubaOS 6.x there is an issue default the Default Destination capability shown in the Web Login configuration. This option is designed to allow you to define an override URL that the wireless/wired user is sent to post authentication. The obvious work around this issue is to set the post authentication URL in the Welcome Page of the ArubaOS Captive Portal Profile. You can leverage the Amigopod skin technology to quickly brand the Captive Portal displayed to the wireless/wired users. These skins are available as a professional service as a purchasable SKU or there are also Custom and Blank Skins available for those customer's that wish to perform their own HTML/CSS style customization. The Title field allows you to customize the Page Title displayed in the Browser. Aruba Networks | 12

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19

ArubaOS + Amigopod Integration Cheet Sheet
Aruba Networks |
12
The IP Address should be set to Aruba Controller IP Address. That is, this address needs to be
available from the wireless/wired client via the
captiveportal
policy on the controller.
As you can see there are several Login Form options that allow you to override the default
Login Form and Labels used to reference User and Password fields. These typically do not
need to be changed.
The
Pre°Auth Check
is only required for Advanced configurations where you might need to
ensure the username and password pair is valid before initiating the RADIUS transaction from
the Aruba Controller. Given the Web Login and RADIUS database is hosted on the same
appliance we can perform a query locally prior to firing a RADIUS transaction.
You can enable the display of an Accept Terms & Conditions option of the login page if
required. This refers to the default T&Cs URL defined under Guest Manager
±
Customization
±
Customize Guest Manager.
Unfortunately, as of ArubaOS 6.x there is an issue default the Default Destination capability
shown in the Web Login configuration. This option is designed to allow you to define an
override URL that the wireless/wired user is sent to post authentication. The obvious work
around this issue is to set the post authentication URL in the Welcome Page of the ArubaOS
Captive Portal Profile.
You can leverage the Amigopod skin technology to quickly brand the Captive Portal displayed
to the wireless/wired users. These skins are available as a professional service as a
purchasable SKU or there are also Custom and Blank Skins available for those customer’s that
wish to perform their own HTML/CSS style customization.
The
Title
field allows you to customize the Page Title displayed in the Browser.