Dell PowerConnect W Clearpass 100 Software ArubaOS Integration Guide - Page 19

Captive Portal Profile Configuration,

Page 19 highlights

Amigopod and ArubaOS Integration Captive Portal Profile Configuration aaa authentication captive-portal "guestnet" default-role auth-guest redirect-pause 3 no logout-popup-window login-page https://10.169.130.50/Aruba_Login.php welcome-page https://10.169.130.50/Aruba_welcome.php switchip-in-redirection-url Application Note NOTE Figure 8 Captive portal profile configuration The example captive portal profile shows the use of HTTPS as the protocol for the redirect URLs for the login and welcome pages. Based on this configuration, the best practice is to install a trusted server certificate on the Amigopod and the controller's web server components of the controller. These trusted server certificates can be obtained from an internal Certificate Authority, if present at the customer site, or various public commercial Certificate Authorities available online. If no trusted server certificate is installed on the Amigopod and the Aruba controller, the user experience will include some browser warning messages regarding the untrusted state of the default certificates. Examples of commercial Certificate Authorities are Verisgn, Thawte, Entrust, GeoTrust, GoDaddy. Aruba Networks, Inc. ArubaOS Configuration | 19

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51

Aruba Networks, Inc.
ArubaOS Configuration
|
19
Amigopod and ArubaOS Integration
Application Note
Captive Portal Profile Configuration
aaa authentication captive-portal "guestnet"
default-role auth-guest
redirect-pause 3
no logout-popup-window
switchip-in-redirection-url
Figure 8
Captive portal profile configuration
NOTE
The example captive portal profile shows the use of HTTPS as the protocol for
the redirect URLs for the login and welcome pages. Based on this
configuration, the best practice is to install a trusted server certificate on the
Amigopod and the controller’s web server components of the controller. These
trusted server certificates can be obtained from an internal Certificate Authority,
if present at the customer site, or various public commercial Certificate
Authorities available online. If no trusted server certificate is installed on the
Amigopod and the Aruba controller, the user experience will include some
browser warning messages regarding the untrusted state of the default
certificates. Examples of commercial Certificate Authorities are Verisgn,
Thawte, Entrust, GeoTrust, GoDaddy.