01-05-2012 02:13 PM
We wanted to centralize our guest access for all sites, so we went ahead and installed Amigopod. We have configured particular settings on the Aruba 3400 controller as well as the Amigopod virtual appliance. However, it is taking the settings from the controller not the appliance (ie- welcome page, password complexity, etc..) is there a way to have all the captive portal settings configured from Amigopod not the controller? Also, when guests first get redirected, IE shows the IP address not the DNS name, anyway to change that as well? thank you
01-05-2012 02:22 PM
If you set the login page in the captive portal profile on the controller to be the Amigopod page, at that point, the settings you state are all based on Amigopod settings. For example:
Amigopod is at IP 126.96.36.199 and you are using a web login page called guest-login.php.
Aruba Controller is using initial-role of guest-logon that uses a CP-Profile of amigopod-cp.
Then edit amigopod-cp profile on Aruba controller to use login page of "http://188.8.131.52/guest-logon.php"
- If you want a DNS name to show, put the DNS name for amigopod in the above instead of IP and make sure that this name resolves to amigopod from the DNS server that guests use.
I am assuming that other integration steps have been completed including:
- Edit guest-logon role (or equivalent) to allow guest clients to open web pages on Amigopod
- Add Amigopod as radius server, add to server-group, and set as server-group in the CP profile used
- Optional: enable interim radius accounting in aaa profile
- Optional: add amigopod as XML server in aaa profile
- Add controller as NAS
01-05-2012 02:23 PM
Have you taken a look at the integration guide we published on setting this up? It's available at http://www.arubanetworks.com/technology/reference-design-guides/, Amigopod and AOS integration.
Director, Strategic Account Solutions
01-05-2012 03:38 PM
Just to add to the other comments, if you wish to define a custom welcome page that is displayed post authentication this will also need to be defined in the captive portal discussed by Austin above. This can not be defined on Amigopod at the moment for the ArubaOS controllers.