This chapter covers the following subjects:
• Plan basic 802.1X deployment on Cisco Catalyst IOS Software: Covers the details of a basic 802.1X deployment.
• Configure and verify Cisco Catalyst IOS Software 802.1X authenticator: Learn how to configure and verify the 802.1X authenticator on Cisco Catalyst IOS Software.
• Configure and verify EAP-FAST on Cisco Secure ACS: The steps necessary to provide EAP-FAST support on Cisco Secure ACS are covered in this section.
• Configure and verify the Cisco Secure Services Client (CSSC) 802.1X supplicant: The 802.1X supplicant is configured in this section.
• Troubleshoot 802.1X on Cisco Identity-Based Network Services (IBNS) components: You learn a process for troubleshooting issues with 802.1X implementations.
This chapter discusses the features of 802.1X authentication. The criticality of authenticating and authorizing access to information assets has never been more important than it is today. Organizations rely more heavily on digital information to increase their success. However, access to that same digital information by the wrong party can also bring about the demise of organizations. Cisco Identity-Based Network Services (IBNS) can use the features of 802.1X to ensure that users and machines that access a company’s resources are properly authenticated and authorized before that access is granted.
The “Do I Know This Already?” quiz helps you decide whether you really need to read the entire chapter. If you already intend to read the entire chapter, you do not necessarily need to answer these questions now.
The ten-question quiz, derived from the major sections in the “Foundation Topics” portion of this chapter, helps you determine how to spend your limited study time.
Table 6-1 outlines the major topics discussed in this chapter and the “Do I Know This Already?” quiz questions that correspond to those topics.
Table 6-1. “Do I Know This Already?” Foundation Topics Section-to-Question Mapping

The goal of self-assessment is to gauge your mastery of the topics in this chapter. If you do not know the answer to a question or are only partially sure of the answer, you should mark this question wrong for purposes of the self-assessment. Giving yourself credit for an answer that you correctly guess skews your self-assessment results and might provide you with a false sense of security.
1. Which of the following three components comprise Cisco 802.1X authentication?
a. Cisco IOS Software 802.1X authenticator
b. Cisco Secure ACS 4.2 Server
c. Cisco Secure Services Client wired 802.1X supplicant
d. Cisco MARS
e. Microsoft SQL Server
2. Which 802.1X component is also known as the client?
a. Cisco IOS Software 802.1X authenticator
b. Cisco Secure ACS 4.2 Server
c. Cisco Secure Services Client wired 802.1X supplicant
d. Cisco MARS
e. The user
3. Which 802.1X component is the switch or router between the client and the AAA server?
a. Cisco IOS Software 802.1X authenticator
b. Cisco Secure ACS 4.2 Server
c. Cisco Secure Services Client wired 802.1X supplicant
d. Cisco MARS
e. The user
4. Which 802.1X component is also known as the AAA server?
a. Cisco IOS Software 802.1X authenticator
b. Cisco Secure ACS 4.2 Server
c. Cisco Secure Services Client wired 802.1X supplicant
d. Cisco MARS
e. The user
5. Which command adds a RADIUS server to an IOS device’s configuration?
a. router (config)# RADIUS server add
b. router (config)# aaa authentication server RADIUS
c. router (config-if)# ip aaa RADIUS host
d. router (config)# radius-server host
6. What UDP ports are used by Cisco as the default authentication and accounting ports?
a. 67 and 68
b. 1645 and 1646
c. 1812 and 1813
d. 20 and 21
e. None of the answers are correct.
7. What must the Shared Secret field on the Network Configuration screen in Cisco Secure ACS match?
a. The cryptographic key that was entered on the IOS-based switch when defining the RADIUS server
b. The IP address of the switch
c. The password that was entered for the user in the Protected Access Credential file
d. The passphrase used to encrypt data between the AAA server and the authenticator
e. The password entered on the supplicant
8. If the network between the supplicant and the AAA server is trusted, you can deploy user PAC files using which method?
a. Manually by importing a PAC file into each client’s supplicant.
b. Configure the switch to copy the PAC from its flash to the client.
c. Push the PAC to the user from the Windows Server Active Directory store.
d. Automatic (anonymous).
9. What is the tool used to create the CSSC configuration profile?
a. Cisco Secure ACS CSUtil command-line utility
b. dot1x test eapol-capable command
c. CSSC Management Utility
d. Cisco Security Device Manager
10. From where are the CSSC supplicant and the CSSC Management Utility obtained?
a. Included in the IOS image
b. Included in Microsoft Windows Operating Systems
c. Downloaded from Cisco.com
d. Obtain from a TAC engineer
The answers to the “Do I Know This Already?” quiz are found in Appendix A. The suggested choices for your next step are as follows:
• 8 or less overall score: Read the entire chapter. This includes the “Foundation Topics” and the “Exam Preparation” section.
• 9 or 10 overall score: If you want more review on these topics, skip to the “Exam Preparation” section. Otherwise, move on to Chapter 7, “Implementing and Configuring Advanced 802.1X.”
802.1X is an IEEE standard that provides a framework for authenticating and authorizing network devices connected to LAN ports and for preventing access in the event that the authentication and authorization fail. The authentication and authorization process requires a supplicant (client), an authenticator (router, switch, wireless AP, and so on), and an authentication server. This chapter covers basic 802.1X features. You will be able to plan basic 802.1X, perform basic configuration tasks, and troubleshoot basic functionality on Cisco IBNS components.
Figure 6-1 shows the components that come into play when considering 802.1X authentication.

Figure 6-1. Components Included in 802.1X Authentication Process

This client-server-based access control and authentication protocol authenticates each client prior to making any services available to that port. Before a port enters an authorized state, 802.1X allows only Extensible Authentication Protocol over LAN (EAPOL), Cisco Discovery Protocol (CDP), and Spanning Tree Protocol (STP) packets to traverse the port.
Configuring 802.1X port authentication is supported on Layer 2 static access ports, voice VLAN–enabled ports, and Layer 3 routed ports. It is not supported on dynamic ports, trunk ports, or Switched Port Analyzer (SPAN) or Remote SPAN (RSPAN) ports.
In this chapter, the basic 802.1X deployment includes configuring bidirectional, basic authentication on the network edge. The process authenticates the user to the network and the network to the user. The supplicant authenticates the user on the computer but not the computer itself. Machine authentication is discussed in Chapter 7. The credentials in this scenario will be shared secrets (passwords) and utilize EAP-FAST as the protocol between the supplicant and the authentication server. A basic 802.1X deployment involves gathering input parameters, making configuration choices, performing basic configuration tasks, and following some general deployment guidelines.
The Cisco IBNS components discussed are as follows:
• Cisco Catalyst IOS Software 802.1X authenticator
• Cisco Secure ACS 4.2 authentication, authorization, and accounting (AAA) server
• Cisco Secure Services Client (CSSC) 802.1X wired supplicant
Because 802.1X authentication requires several technologies to work together, up-front planning helps ensure the success of the deployment. Part of this planning involves gathering important input information:
• Determine the list of LAN switches that currently allow unauthorized users full access to the network. Use this list to determine which of these devices should be configured with 802.1X and the feature availability on the switches.
• Determine what authentication database (such as Windows AD) is being used for user credentials. This allows you to determine whether you can leverage the same one and make the 802.1X deployment transparent to your users.
• Determine the types of clients being used on the network (platform and operating systems). This is required to choose a compatible supplicant and to configure it appropriately.
• Determine the software distribution mechanism in use by the organization. This will affect provisioning and supporting the supplicant on current and future client workstations.
• Determine whether the network path between the supplicant and the authentication server is trusted. A trusted network path allows an anonymous EAP-FAST implementation, whereas a nontrusted network path requires separate EAP-FAST credentials.
Deploying basic 802.1X authentication involves the following deployment steps:
Step 1: Configure the 802.1X authenticator on a Cisco Catalyst IOS Software switch.
Step 2: On the switch, configure a guest VLAN or a restricted VLAN or tune 802.1X timers (optional).
Step 3: Configure the Cisco Secure ACS AAA server to support EAP-FAST and add a user account to its local database.
Step 4: Configure and deploy the 802.1X supplicant to the client machine. The following section discusses the Cisco Secure Services Client (CSS) on the Windows operating system.
Based on the systems and networks in your environment, you need to make some deployment choices when deploying basic 802.1X authentication:
• Choice of EAP method: There are several EAP methods from which to choose. If you use passwords or one-time passwords, use the following guidelines:
• If you simply use passwords, you can use EAP-Flexible Authentication via Secure Tunneling (FAST) as the outer EAP method and EAP-Microsoft Challenge Handshake Authentication Protocol (MS-CHAPv2) as the inner method. EAP-FAST provides identity protection in that attackers cannot determine the client’s identity. If this does not pose a risk for your environment, you can implement EAP-MSCHAPv2 without the EAP-FAST tunnel protection.
• If you use one-time passwords, you can use EAP-Generic Token Card (GTC) inside EAP-FAST or inside Protected Extensible Authentication Protocol (PEAP). Never deploy standalone EAP-GTC.
• Choice of supplicant: You can choose to use the 802.1X supplicant that is provided by the operating system or a third-party supplicant, such as the Cisco Secure Services Client (CSSC). Consider the following:
• Use the native 802.1X supplicant that is included in the operating system if it provides all the features and functionality that you require and makes provisioning in your environment easier.
• Use the CSSC if you need support for many authentication protocols and a single supplicant that works for wired and wireless authentication.
Use the following general guidelines when deploying basic 802.1X authentication:
• Use a single sign-on (SSO) solution for 802.1X that is scalable for your environment. Ensure that your authentication database enforces a policy that requires strong credential strength.
• Ensure proper analysis prior to deployment. Use a deployment plan that has tested successfully because incorrect parameters or configuration items can deny access to large numbers of users all at once.
• Run a pilot deployment and troubleshoot compatibility issues prior to deploying to the entire production environment.
• Ensure that the many different areas of the organization are represented in the pilot so that your testing mimics production as close as possible.
There are several tasks involved in configuring the Cisco Catalyst IOS Software 802.1X authenticator:

Task 1. Configure a RADIUS server on the network switch and the AAA server.
Task 2. Configure the switch to use AAA and the RADIUS protocol for authentication.
Task 3. Enable 802.1X globally on the switch.
Task 4. Enable 802.1X on access ports that require user authentication on the switch.
Task 5. (Optional) Configure periodic reauthentication.
Task 6. (Optional) Tune timers and thresholds.
Task 7. (Optional) Configure a guest policy on the switch if one is needed.
You have to make some configuration choices when configuring the authenticator:
• You can optionally tune 802.1X EAPOL timers. The default timers set in Cisco IOS Software are configured very conservatively. If you have clients that are not receiving their IP address from the DHCP server, it could be from a lengthy 802.1X authentication process.
• You can optionally configure reauthentication. Optional reauthentication is similar to using a heartbeat connection. In some cases, the switch port to which the host connects is not configured with 802.1X authentication and authentication takes place on an upstream switch. Configuring reauthentication will cause a period of verification to take place, thus ensuring that the client it still connected and that the port remains in the authenticated state.
• You can optionally create a guest network. This can be used for hosts that do not have an 802.1X supplicant or for hosts that fail authentication. The guest network can also be used for users who are not part of the authenticated network. These “guest” users might still need to connect and have limited access, such as connectivity to the Internet, but no connectivity to any internal resources.
The configuration scenario, shown in Figure 6-2, will be to configure the Cisco Catalyst IOS Software 802.1X authenticator using the following information:
• The corporate user will be using an 802.1X supplicant, and there will be a guest without a supplicant that connect to a LAN switch that requires authentication on its user ports.
• The router/authenticator is running the Cisco IOS Software and is configured with 192.168.1.1 as its management IP address.
• VLAN 100 is used for the guest network and will only provide access to the public Internet.
• The AAA server is Cisco Secure ACS 4.2, is running on Windows Server with an IP address of 10.1.1.1, and is configured with RADIUS for 802.1X communications.
Figure 6-2. Configuration Scenario

The first task for enabling the Cisco IOS Software 802.1X authenticator is to configure a RADIUS server:
Step 1: Enter the radius-server host command to specify the IP address of the RADIUS server with which the switch will communicate to authenticate 802.1X clients. This command also specifies the cryptographic authentication key that is used to protect the session.
Configure two RADIUS servers to provide a redundant set of AAA servers. Also, use a strong value for the authentication key and consider using different authentication keys for each 802.1X switch, in case one of them gets compromised.
Step 2: Optionally, you can change the authentication and accounting ports from the defaults, UDP 1645 and 1646, which are used by Cisco Secure ACS to the standard RADIUS ports, UDP 1812 and 1813.
Example 6-1 shows the configuration of a RADIUS server at 10.1.1.1, using the standard RADIUS ports, UDP 1812 and 1813, and specifying an authentication key of “rad123.”
Example 6-1. Configure a RADIUS Server on the Cisco Catalyst IOS Software Switch
Router# configure terminal
Router(config)# radius-server host 10.1.1.1 auth-port 1812 acct-port 1813 key rad123
Router(config)# exit
Router# copy running-config startup-config
In Task 2, you enable AAA and configure an AAA authentication method that uses RADIUS for interfaces that will be running 802.1X port security:
Step 1: Enable AAA globally on the switch with the aaa new-model command.
Step 2: Configure an AAA authentication method that specifies that 802.1X authentication requests should be sent to the configured RADIUS servers.
Example 6-2 shows the commands that will enable AAA globally on the switch and then create an AAA authentication method that will send 802.1X authentication requests to the configured RADIUS servers.
Example 6-2. Enable AAA Globally and Use RADIUS for Authentication
Router# configure terminal
Router(config)# aaa new model
Router(config)# exit
Router(config)# aaa authentication dot1x default group radius none
Router# copy running-config startup-config
Tasks 3 and 4 configure 802.1X globally and then enable 802.1X on user (access) ports on the switch:
Step 1: Enable 802.1X globally on the switch with the dot1x system-auth-control global command.
Step 2: On the ports that will require 802.1X authentication, ensure that the interface is configured as a Layer 2 access port with the switchport mode access interface command.
Step 3: Make sure that the user interfaces are assigned to a proper access VLAN with the switchport access vlan vlan-id interface command.
Step 4: Enable 802.1X port control on the user interfaces using the authentication port-control interface command.
Example 6-3 shows the commands that will enable AAA globally on the switch and then create a AAA authentication method that will send 802.1X authentication requests to the configured RADIUS servers.
Example 6-3. Enable 802.1X Globally and Add New RADIUS Authentication Method
Router# configure terminal
Router(config)# dot1x system-auth-control
Router(config)# interface FastEthernet 2/1
Router(config-if)# switchport mode access
Router(config-if)# switchport access vlan 90
Router(config-if)# authentication port-control auto
Router(config)# end
Router# copy running-config startup-config
Task 5 is an optional task that you can configure on an interface or range of interfaces. By default, 802.1X reauthentication is not enabled. This can cause problems in an environment in which not all switches perform authentication. For example, if your distribution switches perform 802.1X authentication, the switch will not detect that the client has disconnected and leave the port in an authenticated state. Periodic reauthentication can alleviate this by forcing the client to periodically reauthenticate to the AAA server.
Step 1: Enable periodic reauthentication on a user interface or range of interfaces with the authentication periodic interface command. The default is that periodic reauthentication is disabled.
Step 2: You can adjust the timer on the periodic reauthentication attempts with the authentication timer reauthenticate interface command. The default time between attempts is 3600 seconds. Reducing the time causes your user ports to be reauthenticated more often. This would be considered good from a security standpoint but will add extra load on your RADIUS servers. Proceed with caution, because a high load could cause legitimate clients to be denied access to your network if your AAA servers are too busy to process 802.1X authentication requests.
Example 6-4 shows the commands that enable periodic reauthentication and adjust the time between periodic reauthentication attempts.
Example 6-4. Enable 802.1X Periodic Reauthentication and Adjust the Time Between Reauthentication Attempts
Router# configure terminal
Router(config)# interface FastEthernet 2/1
Router(config-if)# authentication periodic
Router(config-if)# authentication timer reauthentication 600
Router(config)# end
Router# copy running-config startup-config
Task 6 is an optional task in which you can adjust EAPOL timers to optimize the 802.1X authentication exchange between the supplicant and the authenticator.
Figure 6-3 shows the message exchange between the supplicant and the authenticator (ISR) and the authenticator (ISR) and the authentication server.
Figure 6-3. 802.1X Authentication Message Exchange


EAPOL is used between the supplicant and the authenticator, while RADIUS is used between the authenticator and the authentication server.
The authenticator expects to receive the EAP-Response/Identity frame as a response to its EAP-Request/Identity frame. If it has not received this frame within the default retransmission time, it will resend the Request frame. The default retransmission timer is 30 seconds. You can adjust this time to increase response times, which will allow a faster 802.1X authentication process. The retransmission timer is changed with the dot1x timeout tx-period interface command.
If the switch fails to authenticate a client, such as the user entering a bad password, the switch waits a period of time before trying again. The default value for this quiet timer is 60 seconds. You can lower this value, thus giving the client a faster response time with the dot1x timeout quiet-period seconds interface configuration command.
Example 6-5 shows the commands that change the retransmission and quiet 802.1X timers.
Example 6-5. Change the Default Retransmission and Quiet Timers
Router# configure terminal
Router(config)# interface FastEthernet 2/1
Router(config-if)# dot1x timeout tx-period 10
Router(config-if)# dot1x timeout quiet-period 10
Router(config)# end
Router# copy running-config startup-config
In Task 7, a special-purpose VLAN is designated for clients that either fail authentication or that do not have an 802.1X supplicant. This means that the client does not respond to EAPOL requests and must be placed into a “guest” VLAN. The VLAN used for each of these can be the same or different depending upon your architecture; however, it must exist on the switch before assigning users to it. In the case of authentication failure, you must specify the number of times that the switch should retry authentication before assigning the user to the restricted VLAN. The command for this is authentication event fail retry number action authorize vlan. The command to assign a user to the guest VLAN is authentication event no-response action authorize VLAN.
The 802.1X authentication attempt must fail before the switch will assign the user to the guest VLAN. This time can be configured to be shorter on the interfaces upon which you expect to have guest connections by using the dot1x timeout quiet-period and dot1x timeout tx-period commands.
Example 6-6 shows the commands that assign an interface to a special VLAN for either guests or clients that fail authentication.
Example 6-6. Commands to Configure Guest and Authentication Failed Policy
Router# configure terminal
Router(config)# interface FastEthernet 2/1
Router(config-if)# authentication event fail retry 2 action authorize vlan 100
Router(config-if)# authentication event no-response action authorize vlan 100
Router(config)# end
Router# copy running-config startup-config
Misconfiguration of the 802.1X authenticator can render entire sections of the network unreachable to your users. Extreme caution and planning must be employed when configuring 802.1X authentication. Some guidelines to consider are as follows:
• Adjusting EAPOL timers on interfaces configured with guest policies must be tested prior to implementing in production. Trying to speed up the process for guest users (because authentication must time out) by shortening the time that a switch waits could cause your legitimate users to be placed in the guest VLAN.
• Adjusting timers on the switch might require adjusting timers on the client supplicant as well.
• Ensure that you utilized several security layers in your design to adequately protect the rest of your network from the guest VLAN. You might even consider putting them in a separate Virtual Routing and Forwarding (VRF) instance. VRFs are configurations on Cisco IOS Software routers and switches that can be used to provide traffic separation, making them a good solution to keep guest traffic segregated from your corporate traffic.
To verify the operational status of the 802.1X configuration on your device, use the show dot1x command, which will show the current state of the authenticator as Enabled. Example 6-7 displays the output of the show dot1x command.
Example 6-7. show dot1x Command Output
Router# show dot1x
Sysauthcontrol Enabled
Dot1x Protocol Version 2
The show dot1x all summary command, shown in Example 6-8, shows the authorization state of each of the interfaces on which you have 802.1X authentication configured.
Example 6-8. show dot1x all summary Command Output
Router# show dot1x all summary
Interface PAE Client Status
------------------------------------------------------------------------------------------
Fa1 AUTH 000d.bcef.bfdc AUTHORIZED
Extensible Authentication Protocol - Flexible Authentication via Secured Tunnel (EAP-FAST) is a client-server security architecture that protects EAP transactions by use of a Transport Layer Security (TLS) tunnel. These tunnels are built using shared secrets that are called Protected Access Credentials (PAC).
There are several tasks involved in configuring Cisco Secure ACS for EAP-FAST:
Task 1. Configure a RADIUS server on the network switch and the AAA server.
Task 2. Configure EAP-FAST on the AAA server.
Task 3. Populate the user authentication database on the AAA server.
Task 4. (Optional) Generate user PAC files.
Task 5. (Optional) Configure Network Access Restrictions (NAR) for 802.1X users.
Task 6. Enable logging of passed authentications.
Prior to implementation, several configuration choices must be made:
• Deciding whether to use Network Access Restrictions (NAR). NAR can be used to impose additional restrictions on your users before permitting them to be successfully authenticated. For example, you can restrict them to access the network only from a certain network address space. There are many options available when configuring NAR.
• Deciding how to provision the Protected Access Credential (PAC) files is important. If the network between the AAA server and the switch is a fully trusted path, you can use automatic provisioning of the PAC files. If the path is not trusted, you should provision the PAC files manually.
• Deciding where you user credentials database will reside is also a very important design consideration. Use the Cisco Secure ACS internal database or use an external database that Cisco Secure ACS will contact for authentication validation. Using an external database, such as Windows Active Directory, will make administration much easier and enable single sign-on for the users.
The configuration scenario will be to configure the Cisco Secure ACS EAP-FAST server using basic 802.1X. The client will either be using an 802.1X supplicant or will be a guest without a supplicant. Additionally, the client will connect to a LAN switch that requires authentication on its user ports and will use usernames and passwords to authenticate to the AAA server using EAP-MSCHAPv2 tunneled inside EAP-FAST. The router/authenticator is running the Cisco IOS Software and is configured with 192.168.1.1 as its management IP address. VLAN 100 is used for the guest network and will only provide access to the public Internet. The AAA server is Cisco Secure ACS 4.2 and is running on Windows Server with an IP address of 10.1.1.1 and is configured with RADIUS for 802.1X communications.
For Cisco Secure ACS to authenticate 802.1X clients, the 802.1X-enabled switch/router/AP must be added as a AAA client on the Cisco Secure ACS server. For the first task of configuring the switch/router/AP as a RADIUS AAA client on Cisco Secure ACS, refer to Figure 6-4 and perform the following steps:
Step 1: Click Network Configuration in the navigation bar. The Network Configuration window, shown in Figure 6-4, opens.
Figure 6-4. Network Configuration on Cisco Secure ACS Server

Step 2: Click Add Entry below the AAA clients table.
Step 3: Enter the name of the switch in the AAA Client Hostname field.
Step 4: Enter the IP address of the switch in the AAA Client IP Address field.
Step 5: Enter the session key in the Key field. This is the same key that you configured on the switch in the aaa-server host command used to add the RADIUS server to the switch.
Step 6: Choose RADIUS (Cisco IOS/PIX) from the Authenticate Using drop-down box.
Step 7: Click the Submit + Restart button.
Figure 6-4 shows a AAA client named AP with an IP address of 10.0.0.106 being added to the Cisco Secure ACS server using a shared key of sharedsecret. The protocol used to communicate between the AAA server and the switch is RADIUS (Cisco/PIX).
Failure to add the switch/router/AP to the Cisco Secure ACS server as a AAA client causes authentication attempt from your clients to fail. The AAA server treats the request as coming from an unknown source.
In the second configuration task, refer to Figure 6-5 to enable EAP-FAST on Cisco Secure ACS and configure some of its basic properties.
Step 1: Click System Configuration in the navigation bar. The System Configuration window opens (not shown).
Figure 6-5. System Configuration > Global Authentication Setup

Step 2: Click Global Authentication Setup. The System Configuration > Global Authentication Setup window opens (not shown).
Step 3: Enable EAP-FAST by selecting the check box next to the appropriate option.
Step 4: In the Authority ID Info field, enter a unique name for this server, such as its host name. The example in Figure 6-5 has entered Cisco as the Authority ID.
Step 5: Select the check box next to Allow Anonymous In-band PAC Provisioning if you are using a completely trusted link over which PAC files can be distributed anonymously (without authentication). If the link is not trusted, you should leave this deselected and use manual distribution of the PAC files. The PAC files must be manually imported into the 802.1X supplicant on the client.
Step 6: In the Protocols section of the Network Access Profile (NAP) configuration window (not shown), select the check box next to EAP-MSCHAPv2 under Allowed Inner Methods. This chooses EAP-MSCHAPv2 as the inner authentication method that will authenticate the user to the AAA server.
Step 7: Click the Submit + Restart button.
Perform the following steps to create user accounts in the internal Cisco Secure ACS database. An external authentication database can be used instead. The third configuration task details how to create user accounts, as shown in Figure 6-6.
Step 1: Click User Setup in the navigation bar. The User Setup window opens, as shown in Figure 6-6.
Figure 6-6. ACS User Setup Window

Step 2: Enter a unique username in the User field and click Add/Edit. The Edit User window opens (not shown).
Step 3: In the Edit User screen, provide a password for the user and add the user to a group.
Step 4: Click Submit.
If the network path between the supplicant and the AAA server is not fully trusted, recommended practice dictates manually distributing user PAC files. To use the manual distribution process, PAC files must be generated. In Task 4, the Protected Access Credential (PAC) files for EAP-FAST must be generated and distributed to users to enable the EAP-FAST secure authentication process:
Step 1: Open a command prompt window on the Cisco Secure ACS server as an administrator, as shown in Figure 6-7. Change the directory to a temporary folder.
Figure 6-7. Command Prompt Window for CSUtil

Step 2: Run the CSUtil command with the -t and -a options to generate PAC files.
Step 3: Import the PAC files located in the temporary folder from Step 2 into the supplicant on each user client.
If you use automatic (anonymous) distribution of PAC files, they are transferred to the client during the first EAP-FAST authentication. Manual distribution requires that the files are imported into the 802.1X supplicant for each user.
If the users must be restricted to authentication only from specific RADIUS clients, Network Access Restrictions (NAR) can provide this control. The optional Task 5 shows how to configure NAR to control the locations from which RADIUS users can authenticate:
Step 1: Click Group Setup from the navigation bar. The Group Setup window opens.
Step 2: Click the group that contains the 802.1X user accounts that you want to limit. Click Edit Settings, and the Group Settings page opens.
Step 3: In the Group Settings windows, scroll down to Network Access Restrictions and select the check box to enable Define CLI/DNIS-based Access Restrictions. In the next box, click the device (or device group) from which you want to allow authentication and enter * in the Port, CLI, and DNIS fields. Click Enter to add entries to the list. Figure 6-8 shows this step.
Figure 6-8. ACS Group Setup Screen

Step 4: Click Submit + Restart. Repeat this process for any additional groups to which a NAR must be applied.
Cisco Secure ACS can log successful as well as failed authentication attempts by users. Logging of successful authentication is disabled by default. To verify proper EAP-FAST authentication, follow the steps in Task 6, referring to Figure 6-9, to configure logging of passed authentications:
Step 1: Click System Configuration on the navigation bar. The System Configuration window opens (not shown).
Step 2: Click Logging to open the Logging Configuration window (not shown).
Step 3: Click Configure in the CSV column in the ACS Reports section, and the CSV Passed Authentication File Configuration page opens (not shown).
Step 4: Select the Log to CSV check box.
Figure 6-9. ACS: Enable Logging of Passed Authentications

To provide EAP-FAST authentication on a wired network, you must install and configure the Cisco Secure Services Client (CSSC) by performing the following tasks:
Task 1. Create a CSSC configuration profile using the CSSC Management Utility.
Task 2. Create a wired network profile and policy for authentication.
Task 3. Configure 802.1X timers.
Task 4. Choose authentication mode (user/machine/both).
Task 5. Choose an EAP method.
Task 6. Choose network authentication and login credentials.
Task 7. Create a CSSC installation package including a configuration profile.
Task 8. Install the CSSC package on clients.
The first task involves creating the configuration profile using the CSSC Management Utility. Download the CSSC Management Utility and the CSSC supplicant from Cisco.com. The output of the CSSC Management Utility is an XML file that contains the necessary settings for the client supplicant:
Step 1: Download the CSSC Management Utility and unpack the archive. Run the sscManagementUtility file to open the main screen.
Step 2: Choose Create New Configuration Profile on the main screen.
Step 3: Choose the version of CSSC being used. This chapter uses version 5.1.
The second task creates a wired network profile inside the CSSC configuration profile. Using the CSSC Management Utility, as displayed in Figures 6-10 and 6-11, complete the following steps:
Step 1: Choose a CSSC license option. Using the CSSC for wired only connectivity does not require a license, but if you plan to use the supplicant for both wired and wireless, a CSSC license must be provided on the Client Policy page.
Step 2: Choose Attempt Connection After User Login in the Connection Setting section.
Step 3: Choose to Allow Wired Media and click the Next button.
Step 4: Choose EAP-FAST in the Allowed Authentication Modes on the Authentication Policy page, leaving all other options deselected. Click Next to continue.
Step 5: Click Add Network on the Networks page to add a new network profile.
Step 6: Leave the Wired Network Setting as the default on the Network Media page, and click the Next button.
Step 7: Assign a name to the new network profile on the Wired Network Settings page. Specify the network as an authenticating network by clicking the appropriate radio button in the Security Level section, and then click the Next button.
Figure 6-10. CSSC Client Policy

Figure 6-11. CSSC Authentication Policy

Tasks 3 and 4 optionally tweak timers and choose among user, system, and user plus system authentication. This example will be leaving the 802.1X timers at their default values but will set the authentication mode to user only:
Step 1: The Connection Settings page has four options available through which to tune 802.1X EAPOL parameters for this connection. The parameters, as shown in Figure 6-12, are as follows:
• authPeriod: The time (in seconds) the supplicant will stay in the “authenticating” state while waiting for a response from the switch
• heldPeriod: The time (in seconds) the supplicant will wait after failing authentication before attempting authentication again
• startPeriod: The time (in seconds) the supplicant will stay in the “connecting” state while waiting for an EAP response from the switch
• maxStart: The number of times the supplicant will try to authenticate before giving up
Figure 6-12. Connection Timers

Step 2: Click the Next button to proceed to the next page.
Step 3: Choose the User Connection type on the Network Connection Type page. This causes the connection to only attempt to authenticate the user, not the system.
Task 5 configures the EAP mode that will be used for both the inner and outer authentication types for this connection. The example here chooses EAS-MSCHAPv2 tunneled inside EAP-FAST:
Step 1: Choose EAP-FAST as the outer EAP mode on the User Authentication page, as shown in Figure 6-13. Clicking the Configure button opens the EAP-FAST Settings window, shown in Figure 6-14, and permits you to configure EAP-FAST parameters.
Figure 6-13. User Authentication

Figure 6-14. EAP-FAST Settings

Step 2: Select the Validate Server Identity check box in the EAP Settings window to make the supplicant authenticate the AAA server. In the Credentials Sections of the Inner Method section, choose Authenticate Using a Password and choose EAP-MSCHAPv2 as the inner EAP mode.
Step 3: This step is only required if you are manually distributing user PAC files. Select the Use PACs check box and import the specific PAC file for this user by clicking the Add PAC File button. This file was generated using the CSUtil CLI Utility.
Step 4: Leave all other settings at their default value and click OK.
Step 5: Click the Next button to go to the next page.
Task 6 involves configuring the credentials that will be used to authenticate users to the network (AAA server). Perform the following steps to accomplish this:
Step 1: Click the Next button on the first User Server Validation page because password-based EAP-FAST mode does not require any configuration.
Step 2: On the second User Server Validation page, simply click the Next button again because password-based EAP-FAST authentication does not require trusted certificate authorities.
Step 3: The User Credentials page specifies how the CSSC will get the user’s identity information (username) and authentication credentials (password). Enter a username in the Protected Identity Pattern field. You can optionally enter “[user]” to have a macro automatically select the user’s current Microsoft Windows username as the username.
Step 4: On the same page, select the Prompt for Credentials option and pick the Remember While the User is Logged On option to cache the user’s password. Optionally, you can pick the Use Single Sign On Credentials option to have the Microsoft Windows username and password be used for 802.1X authentication or statically enter the password in the Use Static Credentials option.
Step 5: Click Finish to complete the CSSC Configuration Profile creation.
Task 7 executes the steps needed to create the CSSC Installation Package by bundling the CSSC Configuration Profile created in the previous steps with a CSSC installer to make a custom CSSC installation package for use on a client. Use Figure 6-15 for a visual aid and perform the following steps:
Step 1: Run the sscManagementUtility executable to open the CSSC Management Utility again. The main window will open (not shown).
Step 2: Choose Create Pre-Configured Client Component, and the Select Pre-Configured Client Components window opens (not shown).
Step 3: Specify the path to the CSSC MSI software installer in the Select Pre-Configured Client Components window. This file would have been downloaded from Cisco.com. The path is specified in the Client Source Package File field.
Step 4: Specify the path to the CSSC configuration profile that was created in the previous steps in the Processed and Signed Configuration File field.
Step 5: Specify the location to which the custom CSSC Installation Package will be saved in the Client Destination Package File field.
Step 6: Click Finish to create the custom package.
Figure 6-15. Create a Preconfigured Client Package

If everything was configured correctly, the next time an attempt is made to connect to an 802.1X-authenticated network, the CSSC supplicant will start automatically and a pop-up window will appear asking for a password to be entered. Type in the password, and the client will be authenticated and granted access to the network.
To successfully troubleshoot 802.1X authentication issues, you must consider all the components. These components include the supplicant, the authenticator, and the AAA server and the network connectivity between them. Figure 6-16 depicts the 802.1X authentication components.
Figure 6-16. 802.1X Authentication Components

To troubleshoot 802.1X operation, perform the following steps:
Step 1: Verify the configuration of the client’s supplicant. Use the Cisco IOS Software command dot1x test eapol-capable to verify that the supplicant responds to EAPOL requests. If it does not, check its configuration using the CSSC GUI or the Management Utility. If the supplicant proves to be configured correctly and is responding to EAPOL requests, proceed to the next step.
Step 2: Verify that RADIUS and EAP connections are set up correctly. Checking the logs on the switch while using the test aaa command can reveal RADIUS issues between the switch and the AAA server. Also, check the Cisco Secure ACS Failed Authentication Attempts report to verify that there are no errors on the AAA server. If there appears to be no problem in these areas, move to the next step.
Step 3: Look for user credential problems such as bad passwords in the ACS Failed Attempts log. Also, look for external database errors if using an external authentication database such as Microsoft Windows Active Directory.
By default, 802.1X authentication issues will be logged by Cisco IOS Software. Check logging messages by running the show logging command to verify successful authentication.
The Cisco Secure Services Client (CSSC) installs a system tray icon that can be used to gather information regarding connection status. The tray icon’s color and shape give indication to connection status. In addition, right-clicking the icon provides detailed connection status by choosing the Connection Status icon from the context menu.
The Cisco Secure ACS server provides detailed audit information in the Passed Authentication report. The report shows all successful authentications, whether they are against the internal database or against an external authentication database.
Verifying that interfaces utilized by guest users are assigned to the designated guest VLAN is a very important security requirement. You do not want a misconfiguration to allow a guest user to be connected to an internal production network. The show interfaces status command will show the connected status of your interfaces along with the VLAN to which the interfaces is assigned.
The Cisco IOS Software command dot1x test eapol-capable can verify that the 802.1X authentication infrastructure is functioning properly before enforcing it. This test verifies the supplicant, the authenticator, and the AAA server. The output of the command will show which interfaces have an EAPOL-capable client attached. The switch will wait 10 seconds by default for a response from the supplicant on the client. The dot1x test timeout command can be used to change this timeout to a value range of 1 to 65,535 seconds.
The Cisco IOS Software logging mechanism will provide detailed information to use when troubleshooting a nonresponsive supplicant. Log messages can reveal messages that can indicate that no response was received from the supplicant, a response was received but authentication configurations between the supplicant and the AAA server are mismatched, successful authentications, and so on.
When there is a configuration issue between the RADIUS configuration on the switch and the Cisco Secure ACS server, consult the switch logs as well as the Failed Authentication Attempts report. This report provides detailed messages that can be used to resolve issues.
When a user supplies invalid credentials, the Cisco IOS Software logs will display a failed authentication message. The authenticator (switch) will be notified of the invalid credentials in the form of a RADIUS message sent from the AAA server to the switch. The Cisco Secure ACS server Failed Authentication Attempts report will also indicate bad passwords.
As mentioned in the section, “How to Use This Book,” in the Introduction, you have several choices for exam preparation: the exercises here, the memory tables in Appendix D, the final exam preparation chapter, and the exam simulation questions on the CD-ROM. The following questions present a bigger challenge than the exam itself because they use an open-ended question format. By using this more difficult format, you exercise your memory better and prove your conceptual and factual knowledge of this chapter. You can find the answers to these questions in Appendix A, “Answers to the DIKTA Quizzes and Fill in the Blanks Questions.”
Review the most important topics in this chapter, noted with the Key Topics icon in the margin of the page. Table 6-2 lists a reference of these key topics and the page numbers on which each is found.

Print a copy of Appendix C, “Memory Tables” (found on the CD), or at least the section for this chapter, and complete the tables and lists from memory. Appendix D, “Memory Table Answers,” also on the CD, includes completed tables and lists to check your work. Although there were no memory tables in this chapter, you will find some for other chapters.
Define the following key terms from this chapter, and check your answers in the Glossary:
NIST Special Publication 800-120 - Recommendation for EAP Methods Used in Wireless Network Access Authentication, http://csrc.nist.gov/publications/nistpubs/800-120/sp800-120.pdf.
802.1X IEEE Standard for Local and Metropolitan Area Networks – Port-based Network Access Control, http://standards.ieee.org/getieee802/download/802.1X-2004.pdf.
Configuring IEEE 802.1x Port-Based Authentication - Cisco IOS Configuration Guide 12.4, www.cisco.com/en/US/docs/ios/sec_user_services/configuration/guide/sec_cfg_ieee802_pba_ps6441_TSD_Products_Configuration_Guide_Chapter.html.
Catalyst 6500 Release 12.2SXH and Later Software Configuration Guide; Configuring IEEE 802.1X Port-Based Authentication, www.cisco.com/en/US/partner/docs/switches/lan/catalyst6500/ios/12.2SX/configuration/guide/dot1x.html.
Cisco Secure ACS: Network Access Restrictions with AAA Clients for Users and User Groups, www.cisco.com/en/US/partner/products/sw/secursw/ps2086/products_tech_note09186a0080858d3c.shtml.