Home > Wireless LAN > Encryption and Authentication > Configuring WPA2 Enterprise with RADIUS using Cisco ISE

Configuring WPA2 Enterprise with RADIUS using Cisco ISE

Cisco Meraki access points can be configured to provide enterprise WPA2 authentication for wireless networks using Cisco Identity Services Engine (ISE) as a RADIUS server. This article will cover instructions for basic integration with this platform. For more detailed information on how to configure Cisco ISE, please refer to the Cisco Identity Services Engine User Guide.


Installing Server Certificates 

After installation, Cisco ISE generates, by default, a self-signed local certificate and private key, and stores them on the server. This certificate will be used by default for WPA2-Enterprise. In a self-signed certificate, the hostname of Cisco ISE is used as the common name (CN) because it is required for HTTPS communication.

Note: Using a self-signed certificate is not recommended for RADIUS, in order to use the default self-signed cert, clients will need to be configured to not validate the RADIUS server's identity. Please refer to our RADIUS documentation for certificate options on the RADIUS server.

Adding Managed Network Devices

  1. In Cisco ISE, choose Administration > Network Resources > Network Devices.
  2. From the Network Devices navigation pane on the left, click Network Devices.
  3. Click Add, or check the check box next to a device and click Edit to edit it or click Duplicate to create a duplicate entry. You can alternatively click Add new device from the action icon on the Network Devices navigation pane or click a device name from the list to edit it.
  4. In the right pane, enter the Name and IP Address.
  5. Check the Authentication Settings check box and define a Shared Secret for RADIUS authentication. This must match the Secret entered for the RADIUS server when configuring the SSID in Dashboard.
  6. Click Submit.

Enabling Policy Sets

Cisco ISE supports policy sets, which allows grouping sets of authentication and authorization policies. As opposed to the basic authentication and authorization policy model, which is a flat list of authentication and authorization rules. Policy sets allow for logically defining an organization's IT business use cases into policy groups or services, such as VPN and 802.1X. This makes configuration, deployment, and troubleshooting much easier.

  1. In Cisco ISE, choose Administration > System > Deployment > Settings > Policy Sets.
  2. Click the Default policy. The default policy is displayed in the right.
  3. Click the plus (+) sign on top and choose Create Above.
  4. Enter the Name, Description and a Condition for this group policy.
  5. Define the Authentication policy.
  6. Click Submit. After configuring a policy set, Cisco ISE will log out any administrators. Log in again to access the Admin portal.

Configuring an Authentication Policy

  1. In Cisco ISE, select the Actions menu and click Insert New Rule Above.
  2. Give the sub-rule a Name (Example: Dot1X).
  3. Click the small window icon to open the Conditions menu.
  4. Select Create New Condition (Advanced Option).
  5. Select Network Access > Eap Authentication.
  6. Leave the operator box set to EQUALS.
  7. In the last box select EAP-MSCHAPv2.
  8. In the Use field, select Active Directory as the identity store. Configure the Active Directory integration as appropriate for the desired deployment.
Last modified



This page has no classifications.

Explore the Product

Click to Learn More

Article ID

ID: 2078

Explore Meraki

You can find out more about Cisco Meraki on our main site, including information on products, contacting sales and finding a vendor.

Explore Meraki

Contact Support

Most questions can be answered by reviewing our documentation, but if you need more help, Cisco Meraki Support is ready to work with you.

Open a Case

Ask the Community

In the Meraki Community, you can keep track of the latest announcements, find answers provided by fellow Meraki users and ask questions of your own.

Visit the Community