Dell PowerConnect W Clearpass 100 Software HP ProCurve MSM Integration Guide - Page 35

Step 4 - Launch Web Browser and login

Page 35 highlights

Step 4 - Launch Web Browser and login When the web browser on the test laptop is launched the MSM will automatically capture the session and redirect the user to the amigopod hosted login page as shown below (which was defined in the Public Access LOGIN-URL) Enter the test user details entered and recorded in Step 1 above and click the Login button. At this point the test user should be successfully authenticated and allowed to transit through the controller and onto the Internet or Corporate network. Note: If the web browser fails to redirect check that the DNS server configured in the base Trapeze configured defined before Step 1 is available and successfully resolving domain names. Without name resolution working the web browser will never attempt to connect to the website defined in web browser home page and therefore there is no session for the HP ProCurve controller to redirect. Other situations that can cause issues with the captive portal include but are not limited to: • Web browser home page set to intranet site not available in current DNS • Proxy Server configuration in browser using non standard HTTP ports CONFIDENTIAL 35

  • 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

CONFIDENTIAL
35
Step 4 – Launch Web Browser and login
When the web browser on the test laptop is launched the MSM will automatically capture the
session and redirect the user to the amigopod hosted login page as shown below (which was
defined in the
Public Access
LOGIN-URL
)
Enter the test user details entered and recorded in Step 1 above and click the
Login
button.
At this point the test user should be successfully authenticated and allowed to transit through
the controller and onto the Internet or Corporate network.
Note:
If the web browser fails to redirect check that the DNS server configured in the base
Trapeze configured defined before Step 1 is available and successfully resolving domain
names. Without name resolution working the web browser will never attempt to connect to the
website defined in web browser home page and therefore there is no session for the HP
ProCurve controller to redirect. Other situations that can cause issues with the captive portal
include but are not limited to:
Web browser home page set to intranet site not available in current DNS
Proxy Server configuration in browser using non standard HTTP ports