AMIGOPOD PowerConnect W Clearpass 100 Software Integration Manual page 9

Amigopod and ArubaOS Integration
Table 2 Comparison of ArubaOS Captive Portal and Amigopod (Continued)
Feature
Enterprise Features and Scalability
Managing 1000s of accounts
High availability/redundancy
Expandability (plug-in architecture)
Although ArubaOS supports internal and external captive portal functionality, this guide focuses on
external captive portal functionality. The internal captive portal dictates the use of the internal login
page on the controller itself. The login page is very basic and does not allow for the extensive
customization that is possible with the Amigopod Web Logins feature.
Amigopod provides the Skin plugin technology where the presentation of the UI
is separated from the mechanics of the underlying application. This separation
allows Aruba to supply end users with a branded skin for all Amigopod
interaction (both visitor and administrators) for a nominal fee at the time of
purchase. Users can also customize the skin themselves with the requisite
N O T E
skills. ArubaOS now allows for fully customized captive portal pages to be
uploaded to the controller. However, this process requires a significant amount
of web design and JavaScript experience to produce a professional result.
The integration of Amigopod with the mobility controller also leverages the ability of ArubaOS to define
and reference external RADIUS servers for the authentication and accounting of visitor accounts. In
the standalone Aruba guest-provisioning solution, the local database in each controller stores user
credentials, which limits the solution to the scope of the local deployment. With the introduction of
Amigopod, all visitor accounts are created, authenticated, and accounted for on the Amigopod internal
RADIUS server.
Aruba Networks, Inc.
ArubaOS Plus
ArubaOS
Captive Portal Authentication
Application Note
Amigopod
| 9