• Encrypted configuration files
• Settings Access (can limit user access to configuration menus)
Extensible Authentication Protocol - Flexible Authentication via Secure Tunneling (EAP-FAST)
Extensible Authentication Protocol - Flexible Authentication via Secure Tunneling (EAP-FAST) encrypts EAP transactions
within a Transport Level Security (TLS) tunnel between the access point and the Remote Authentication Dial-in User Service
(RADIUS) server such as the Cisco Access Control Server (ACS) or Cisco Identity Services Engine (ISE).
The TLS tunnel uses Protected Access Credentials (PACs) for authentication between the client (the Cisco IP Phone 8861 and
8865) and the RADIUS server. The server sends an Authority ID (AID) to the client, which in turn selects the appropriate PAC.
The client returns a PAC-Opaque to the RADIUS server. The server decrypts the PAC with its master-key. Both endpoints now
have the PAC key and a TLS tunnel is created. EAP-FAST supports automatic PAC provisioning, but it must enable don the
RADIUS server.
To enable EAP-FAST, a certificate must be installed on to the RADIUS server.
The Cisco IP Phone 8861 and 8865 currently support automatic provisioning of the PAC only, so enable Allow anonymous in-
band PAC provisioning on the RADIUS server as shown below.
Both EAP-GTC and EAP-MSCHAPv2 must be enabled when Allow anonymous in-band PAC provisioning is enabled.
EAP-FAST requires that a user account be created on the authentication server.
If anonymous PAC provisioning is not allowed in the production wireless LAN environment then a staging RADIUS server can
be setup for initial PAC provisioning of the Cisco IP Phone 8861 and 8865.
This requires that the staging RADIUS server be setup as a slave EAP-FAST server and components are replicated from the
product master EAP-FAST server, which include user and group database and EAP-FAST master key and policy info.
To Next Page
Loading...
Need help?
General
