Filter
Top Products
9-7
Cisco IOS Software Configuration Guide for Cisco Aironet Access Points
OL-30644-01
Chapter 9 Configuring an Access Point as a Local Authenticator
Configuring a Local Authenticator
Each time the access point tries to use the main servers while they are down, the client device trying to
authenticate might report an authentication timeout. The client device retries and succeeds when the
main servers time out and the access point tries the local authenticator. You can extend the timeout value
on Cisco client devices to accommodate expected server timeouts.
To remove the local authenticator from the access point configuration, use the no radius server radserv
global configuration command.
Configuring EAP-FAST Settings
The default settings for EAP-FAST authentication are suitable for most wireless LANs. However, you
can customize the credential timeout values, authority ID, and server keys to match your network
requirements.
Configuring PAC Settings
This section describes how to configure Protected Access Credential (PAC) settings. The first time that
an EAP-FAST client device attempts to authenticate to the local authenticator, the local authenticator
generates a PAC for the client. You can also generate PACs manually and import PAC files manually on
the client.
PAC Expiration Times
You can limit the number of days for which PACs are valid, and a grace period during which PACs are
valid after they have expired. By default, PACs are valid for 2 days (one day default period plus one day
grace period). You can also apply the expiration of time and the grace period settings to a group of users.
Use this command to configure the expiration time and grace period for PACs:
AP(config-radsrv-group)# [no] eapfast pac expiry days [grace days]
Enter a number of days from 2 to 4095. Enter the no form of the command to reset the expiration time
or grace period to infinite days.
In this example, PACs for the user group expire in 100 days with a grace period of two days:
AP(config-radsrv-group)# eapfast pac expiry 100 grace 2
Generating PACs Manually
The local authenticator automatically generates PACs for EAP-FAST clients that request them. However,
you might need to generate a PAC manually for some client devices. When you enter the command, the
local authenticator generates a PAC file and writes it to the network location that you specify. The user
imports the PAC file into the client profile.
Use this command to generate a PAC manually:
AP# radius local-server pac-generate username filename [password password] [expiry days]
When you enter the PAC filename, enter the full path to which the local authenticator writes the PAC file
(such as tftp://172.1.1.1/test/user.pac). The password is optional and, if not specified, a default password
understood by the CCX client is used. Expiry is also optional and, if not specified, the default period is
1 day.