This document describes Cisco Identity Services Engine (ISE) compatibility with switches, wireless LAN controllers, and other policy enforcement devices as well as operating systems with which Cisco ISE interoperates.
Cisco ISE supports interoperability with any Cisco or non-Cisco RADIUS client network access device (NAD) that implements common RADIUS behavior (similar to Cisco IOS 12.x) for standards-based authentication. For a list of supported authentication methods, see the “Configuring Authentication Policies” chapter of the Cisco Identity Services Engine User Guide, Release 1.2.
Certain advanced use cases, such as those that involve posture assessment, profiling, and web authentication, are not consistently available with non-Cisco devices or may provide limited functionality, and are therefore not supported with non-Cisco devices. In addition, certain other advanced functions like central web authentication (CWA), Change of Authorization (CoA), Security Group Access (SGA), and downloadable access control lists (ACLs), are only supported on Cisco devices. For a full list of supported Cisco devices, see Table 1.
The NADs that are not explicitly listed in Table 1 and do not support RADIUS CoA must use inline posture.
Note Some switch models and IOS versions may have reached the end-of-life date and interoperability may not be fully supported.
To support the Cisco ISE profiling service, use the latest version of NetFlow, which has additional functionality that is needed to operate the profiler. If you use NetFlow version 5, then you can use version 5 only on the primary NAD at the access layer, as it will not work anywhere else.
1.The “Recommended OS Version” is based on releases that contain both core and advanced ISE feature support and have been tested with Cisco ISE release 1.2.x. This table is not a representation of all possible OS versions supported by ISE. The OS versions not listed may be supported with limited features, may contain critical defects for selected features, and have not been fully tested with Cisco ISE 1.2.x. While selecting an OS version, it is recommended to refer to the OS documentation for the required Cisco ISE feature support and outstanding defects.
2.Cisco Wireless LAN Controllers (WLCs) and Wireless Service Modules (WiSMs) do not support downloadable ACLs (dACLs), but support named ACLs. Autonomous AP deployments do not support the requirements for Inline Posture Node as they do not send Framed-IP-Address. Profiling services are supported for 802.1X-authenticated WLANs starting from WLC release 22.214.171.124 and for MAB-authenticated WLANs starting from WLC 126.96.36.199. FlexConnect, previously known as Hybrid Remote Edge Access Point (HREAP) mode, is supported with central authentication configuration deployment starting from WLC 188.8.131.52. For additional details regarding FlexConnect support, refer to the release notes for the applicable wireless controller platform.
4.2960 LAN Lite is supported but not recommended with ISE 1.2 due to limited feature support. LAN Lite supports only 802.1X and VLAN assignments.
5.The current available IOS releases for converged access switches, such as 3850 or 3650, may not send Calling-Station-ID in the RADIUS accounting requests, which may result in incorrect session states and endpoint profiles in ISE. Refer to Release Notes for Cisco Identity Services Engine, Release 1.2.x for more information.
6.WLCs prior to release 184.108.40.206 do not support CoA and require deployment of an ISE Inline Posture Node to support posture services.
7.Supports MAC filtering with RADIUS lookup.
8.DNS based ACL feature will be supported in WLC 8.0. Not all Access Points support DNS based ACL. Refer to Cisco Access Points Release Notes for more details.
9.Support for session ID and COA with MAC filtering provides MAB-like functionality.
10.802.1X / MAB with URL redirect is only available on non-800 ISR G2. Web Authentication with URL redirect is not available on all ISR G2 platforms.
11.Requires ISE Version 220.127.116.119—Cumulative Patch 5 or above.
Supported AAA Attributes for Third-Party VPN Concentrators
For third-party VPN concentrators to integrate with Cisco ISE and Inline Posture nodes, the following authentication, authorization, and accounting (AAA) attributes must be included in RADIUS communication:
Calling-Station-Id (for MAC_ADDRESS)
Also, for VPN devices, the RADIUS accounting message must have the framed-ip-address attribute set to the VPN client’s IP address pool.
12.Cisco ISE OCSP functionality is available only on Microsoft Windows Active Directory 2008, 2008 R2, 2012, and 2012 R2.
13.Cisco ISE SCEP functionality is available only on Microsoft Windows Active Directory 2008 R2, 2012, and 2012 R2.
14.Microsoft Windows Active Directory version 2000 or its functional level are not supported by Cisco ISE.
15.Starting from Release 1.2.1, Cisco ISE supports all the legacy features in Microsoft Windows Active Directory 2012 R2; however, the new features in 2012 R2, such as Protective User Groups, are not supported.
Cisco ISE interoperates fully with third-party RADIUS devices that adhere to the standard protocols. Support for RADIUS functions depends on the device-specific implementation.
Cisco ISE conforms to the following RFCs:
RFC 2138—Remote Authentication Dial In User Service (RADIUS)
RFC 2139—RADIUS Accounting
RFC 2865—Remote Authentication Dial In User Service (RADIUS)
RFC 2866—RADIUS Accounting
RFC 2867—RADIUS Accounting Modifications for Tunnel Protocol Support
Supported Browsers for the Admin Portal
Mozilla Firefox version 5. x to 38.05 (applicable for Windows, Mac OS X, and Linux-based operating systems).
Windows Internet Explorer 8. x and later.
Note The Cisco ISE Admin portal does not support using the Microsoft IE8 browser in its IE7 Compatibility Mode (the Microsoft IE8 is supported in its IE8-only mode).
Adobe Flash Player 18.104.22.168 or above must be installed on the system running your client browser.
The minimum required screen resolution to view the Cisco ISE Admin portal and for a better user experience is 1280 x 800 pixels.
Supported Virtual Environments
Cisco ISE supports the following virtual environment platforms:
VMware ESX 4. x
VMware ESXi 4. x
VMware ESXi 5. x
Supported Client Machine and Personal Device Operating Systems, Supplicants, and Agents
Note All standard 802.1X supplicants can be used with Cisco ISE, Release 1.2.x standard and advanced features as long as they support the standard authentication protocols supported by Cisco ISE. (For information on allowed authentication protocols, see the “Managing Authentication Policies” chapter of the Cisco Identity Services Engine User Guide, Release 1.2). For the VLAN change authorization feature to work in a wireless deployment, the supplicant must support IP address refresh on VLAN change.
Cisco NAC Agent Interoperability Between Cisco NAC Appliance and Cisco ISE
The Cisco NAC Agent versions 22.214.171.124 and later can be used on both Cisco NAC Appliance Releases 4.9(1),4.9(3), 4.9(4) and Cisco ISE Releases 1.1.3-patch 11, 1.1.4-patch 11, 1.2.x. This is the recommended model of deploying the NAC agent in an environment where users will be roaming between ISE and NAC deployments.
Client Machine Operating Systems and Agent Support in Cisco ISE
20.When Apple iOS devices use Protected Extensible Authentication Protocol (PEAP) with Cisco ISE or 802.1x, certificate warnings might be displayed even for publicly trusted certificates. This usually occurs when the public certificate includes a Certificate Revocation List (CRL) distribution point that the iOS device needs to verify. The iOS device cannot verify the CRL without network access. Click Confirm or Accept in the iOS device to authenticate to the network.
21.Apple iOS release 9.x and later are qualified with Cisco ISE 1.2.1 patch 7 and later releases.
24.Apple Safari version 6.0 is supported only on Mac OS X 10.7.4 and later versions of the operating system.
25.If you are using Mac OS X clients with Java 7, you cannot download the Agents using Google Chrome browser. Java 7 runs only on 64-bit browsers and Chrome is a 32-bit browser. It is recommended to use either previous versions of Java or other browsers while downloading the Agents.
26.Apple Safari version 6.0 is only supported on Mac OS X 10.7.4 and later versions of the operating system.
27.If you are using Mac OS X clients with Java 7, you cannot download the Agents using Google Chrome browser. Java 7 runs only on 64-bit browsers and Chrome is a 32-bit browser. It is recommended to use either previous versions of Java or other browsers while downloading the Agents.
28.Starting from Mac OS X Agent version 126.96.36.199, Cisco NAC Agent supports automatic update of the Compliance Module on Mac OS X clients. Ensure that you have installed Cisco Identity Services Engine, Release 188.8.131.529 cumulative patch 4 or later so that the Compliance Module gets updated automatically.
29.It is recommended to use the Cisco NAC/Web Agent versions along with the corresponding Cisco ISE version.
30.Microsoft Windows 10 and later are qualified with Cisco ISE 1.2.1 patch 7 and later releases.
31.Microsoft Edge browser does not support NAC Agent provisioning.
32.In Windows 8, Internet Explorer 10 has two modes: Desktop and Metro. In Metro mode, the ActiveX plugins are restricted. You cannot download the Cisco NAC Agent in Metro mode. You must switch to Desktop mode, ensure ActiveX controls are enabled, and then launch Internet Explorer to download the Cisco NAC Agent. (If users are still not able to download Cisco NAC agent, check and enable “compatibility mode.”)
33.When you create a Cisco ISE client provisioning policy to accommodate Windows 8, you must specify the “Windows All” operating system option.
34.Windows 8 RT is not supported.
35.Cisco ISE does not support the Windows Embedded operating systems available from Microsoft.
36.When Internet Explorer 10 is installed on Windows 7, to get full network access, you need to update to March 2013 Hotfix ruleset.
38.Because of the open access-nature of Android implementation on available devices, Cisco ISE may not support certain Android OS version and device combinations.
39.Tested with Cisco ISE, Release 1.2.1 patch 7.
40.Tested with Cisco ISE, Release 1.2.1 patch 7.
41.In Windows 8, Internet Explorer 10 has two modes: Desktop and Metro. In Metro mode, the ActiveX plugins are restricted. You cannot download the Cisco NAC Agent in Metro mode. You must switch to Desktop mode, ensure ActiveX controls are enabled, and then launch Internet Explorer to download the Cisco NAC Agent. (If users are still not able to download Cisco NAC agent, check and enable “compatibility mode.”)
42.Cisco ISE, Release 1.2.1 patch 7 supports Windows 10 operating system and Microsoft Edge browser
43.Cisco ISE does not support the Windows Embedded 7 versions available from Microsoft.
44.When Internet Explorer 10 is installed on Windows 7, to get full network access, you need to update to March 2013 Hotfix ruleset.
Note When a guest user tries to log in using Google Chrome on Windows 7 OS, the login fails. It is recommended to upgrade the browser to Chrome 11.
Supported Devices for On-Boarding and Certificate Provisioning
SPW from Cisco.com or Cisco ISE client provisioning feed
45.Tested with Cisco ISE, Release 1.2.1 patch 7.
46.Connect to secure SSID after provisioning
47.There are known EAP-TLS issues with Android 4.1.1 devices. Contact your device manufacturer for support.
48.Barnes & Noble Nook (Android) works when it has Google Play Store 2.1.0 installed.
49.While configuring the wireless properties for the connection (Security > Auth Method > Settings > Validate Server Certificate), uncheck the valid server certificate option or if you check this option, ensure that you select the correct root certificate.
50.If you are using Mac OS X clients with Java 7, you cannot download the SPWs using Google Chrome browser. Java 7 runs only on 64-bit browsers and Chrome is a 32-bit browser. It is recommended to use either previous versions of Java or other browsers while downloading the SPWs.
Requirements for CA to Interoperate with Cisco ISE
While using a CA server with Cisco ISE, make sure that the following requirements are met:
Key size should be 1024, 2048, or higher. In CA server, the key size is defined using certificate template. You can define the key size on Cisco ISE using the supplicant profile.
Key usage should allow signing and encryption in extension.
While using GetCACapabilities through the SCEP protocol, cryptography algorithm and request hash should be supported. It is recommended to use RSA + SHA1.
Online Certificate Status Protocol (OCSP) is supported. This is not directly used in BYOD, but a CA which can act as an OCSP server can be used for certificate revocation.
Note EJBCA 4.x is not supported by Cisco ISE for proxy SCEP. EJBCA is supported by Cisco ISE for standard EAP authentication like PEAP, EAP-TLS, and so on.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
Subscribe to the What’s New in Cisco Product Documentation as a RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1721R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.