03-29-2018 02:36 PM - edited 07-30-2020 06:59 AM
This document describes how Cisco ISE and the Identity PSK feature on the Cisco WLC can support a unique passphrase for each device on a WPA2-PSK WLAN. To date, Identity PSK implementation guides focused on singular authorization policies; ISE endpoint identity groups for dynamic (device profiling) or static classification of wireless devices.
To learn about Identity PSK, its benefits, and how to configure the Cisco WLC; please read the AireOS 8.5 Identity PSK Feature Deployment Guide.
Identity PSK requires the wireless client's MAC address to be registered or profiled on the ISE server. WLAN association enforcement occurs on the WLC by comparing the client provided passphrase to the passphrase returned as an attribute-value response from the ISE server. Cisco ISE can send additional controls to the WLC in the response, such as VLAN ID, TrustSec SGT, and AireOS ACL name.
Why use per-device passphrases instead of shared passphrases? For many environments, the grouping of devices into endpoint identity groups and using a group passphrase simplifies operations, but the following use cases may benefit from per-device passphrases:
Open the Endpoint Custom Attributes page
Click on the Top Menu: Administration > Identity Management > Settings
Click on the Left Menu: Endpoint Custom Attributes
Create a new Custom Attribute
This will create a new endpoint variable, used for the passphrase in the ISE database.
The example utilizes a custom attribute named: iPSK:
Be certain to cast the custom attribute as type "string."
Register the wireless endpoint using the ISE GUI
Click on the Top Menu: Context Visibility > Endpoints
Click on the "Plus Sign"
Input the endpoint's MAC address, then click Save.
Access to the endpoint passphrase attribute via the Device Registration Portal on ISE is not supported.
To provide device self-registration, a custom web portal can be created - external to Cisco ISE. Cisco ISE provides a RESTful API, which can be used by the custom web portal to register a device and its unique passphrase using API calls.
Developing a custom web portal is outside the scope of this document. For more information regarding the Extensible RESTful Services (ERS) for Cisco ISE, please read about it here.
Just to confirm, are you saying that the minimum OS version for ISE has to be 2.3 in order to run IPSK?
As a reminder, this is a special use case. Please review the AireOS 8.5 Identity PSK Feature Deployment Guide for guidance on typical use. When used in this manner, there isn't a version requirement for Cisco ISE. As a reminder, Identity PSK on the WLC integrates with most RADIUS servers, not just Cisco ISE.
This article requires Cisco ISE 2.3 or newer is to accomplish the special use case: Per-Device PSK. Cisco ISE 2.3 added the capability build a dynamic RADIUS AVP response using a variable (endpoint custom attribute). This simplifies our RADIUS authorization policies. Without it, we would have to create an authorization policy per-endpoint.
... Cisco ISE 2.3 added the capability build a dynamic RADIUS AVP response using a variable (endpoint custom attribute). This simplifies our RADIUS authorization policies. ...
The custom attributes for internal endpoints are there since ISE 2.1. It appears working fine with an authorization profile with an endpoint custom attribute assigned to Cisco AVP, when I tried it with ISE 2.2 Patch 9.
Thanks to you both for your quick feedback and clarification! Creating a policy or even an authZ rule for every every endpoint would be very impractical and tough to manage especially for large customers. Glad to hear that ISE 2.3 can do this dynamically. via RADIUS AVP response.
Another question. Has IPSK been tested with ISE 2.4? If not, is there any plans to test it with ISE 2.4?
Is iPSK supported for an AP running in FlexConnect mode/ local switching/ central authentication?
@kahsieh as mentioned in the beginning its for 2.3 and higher. For iPSK support you should check with the wireless team, however you can also see this information:
According to 8.8mr1 RN Flex + iPSK + p2p blocking is supported:
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: