Dell PowerConnect W Clearpass 100 Software Implementing Accounting-Based Autho - Page 18

Additional Configuration Guidelines

Page 18 highlights

Additional Configuration Guidelines To complete the deployment, ensure that each of the following points has been taken into consideration: • The NAS captive portal should redirect guests to the login page, which will be located at a URL such as: http://amigopod/login.php. • If you are using HTTPS for guest traffic (as recommended by the Amigopod Security Manager), then update the URL accordingly, e.g. https://amigopod/login.php. • If you have used a page name other than login for the login page, then update the URL accordingly, e.g. https://amigopod/acme_login.php. • The NAS should be configured to authenticate guests with the Amigopod RADIUS server. • The NAS should be configured to send session accounting traffic to the Amigopod RADIUS server. • The NAS should be configured to accept dynamic authorization (RFC 3576) requests from the Amigopod RADIUS server. • Use the same shared secret for authentication, accounting and dynamic authorization; on the Amigopod RADIUS server, the shared secret configured for the NAS is used for all three functions. • Interim accounting on the NAS should be enabled where possible; the AcctInterim-Interval RADIUS attribute may be required to enable interim accounting and set the interval, or the interim accounting interval may be configured separately on the NAS. Consult the NAS vendor's documentation for additional details. Refer to the Amigopod integration guide corresponding to your vendor's equipment for additional information about configuring other basic networking aspects of the deployment. Also note that this technical note does not cover guest account provisioning. For details on sponsored account creation, guest self-registration or guest purchased access, refer to the appropriate section in the Amigopod Deployment Guide. 18| Implementing Accounting-Based Authorization Amigopod |Technical Note

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

18
| Implementing Accounting-Based Authorization
Amigopod
|Technical Note
Additional Configuration Guidelines
To complete the deployment, ensure that each of the following points has been taken into
consideration:
The NAS captive portal should redirect guests to the login page, which will be located
at a URL such as:
http://amigopod/login.php
.
If you are using HTTPS for guest traffic (as recommended by the Amigopod Security
Manager), then update the URL accordingly, e.g.
https://amigopod/login.php
.
If you have used a page name other than
login
for the login page, then update the URL
accordingly, e.g.
https://amigopod/acme_login.php
.
The NAS should be configured to authenticate guests with the Amigopod RADIUS
server.
The NAS should be configured to send session accounting traffic to the Amigopod
RADIUS server.
The NAS should be configured to accept dynamic authorization (RFC 3576) requests
from the Amigopod RADIUS server.
Use the same shared secret for authentication, accounting and dynamic authorization;
on the Amigopod RADIUS server, the shared secret configured for the NAS is used for
all three functions.
Interim accounting on the NAS should be enabled where possible; the
Acct-
Interim-Interval
RADIUS attribute may be required to enable interim accounting
and set the interval, or the interim accounting interval may be configured separately
on the NAS. Consult the NAS vendor’s documentation for additional details.
Refer to the Amigopod integration guide corresponding to your vendor’s equipment for
additional information about configuring other basic networking aspects of the
deployment.
Also note that this technical note does not cover guest account provisioning.
For details
on sponsored account creation, guest self-registration or guest purchased access, refer to
the appropriate section in the Amigopod Deployment Guide.