Supported and Interoperable Devices and Software for Cisco Secure Access Control System 5.8
Available Languages
Table of Contents
Supported and Interoperable Devices and Software for Cisco Secure Access Control System 5.8
Supported External Identity Stores
Lightweight Directory Access Protocol Server
Supported Authentication Protocols
ACS 5.8 Remote Database Support
Supported OpenSSH and OpenSSL Versions
Obtain Documentation and Submit a Service Request
Supported and Interoperable Devices and Software for Cisco Secure Access Control System 5.8
The Cisco Secure Access Control System Release 5.8, hereafter referred to as ACS, works with many devices. You can use this document to find devices and software that ACS 5.8 supports.
For details regarding limitations and known problems, see the Release Notes for Cisco Secure Access Control System 5.8.
■
Supported External Identity Stores
■Supported Authentication Protocols
■Supported Authentication Protocols
■ACS 5.8 Remote Database Support
■Supported OpenSSH and OpenSSL Versions
■Obtain Documentation and Submit a Service Request
Supported Devices
ACS 5.8 supports all devices that implement the authentication, authorization, and accounting (AAA) mechanism similar to Cisco IOS 12.x.
RADIUS and TACACS+
ACS fully interoperates with third-party RADIUS and TACACS+ client devices that adhere to the governing protocols. Support for RADIUS and TACACS+ functions, depends on the device-specific implementation. For example, on a specific device:
■TACACS+ might not be available for user authentication and authorization
■RADIUS might not be available for administrative authentication and authorization
For TACACS+ devices, ACS conforms to the TACACS+ protocol as Cisco Systems defined in draft 1.78, which is available at http://www.cisco.com
For RADIUS, ACS conforms to the following Request For Comments (RFC):
■ 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 for Tunnel Protocol Support
■ RFC 2868 — RADIUS Attributes for Tunnel Protocol Support
■ RFC 2869 — RADIUS Extensions
Note: For details regarding the implementation of vendor-specific attributes (VSAs), see the User Guide for Cisco Secure Access Control System 5.8.
Table 1 lists some of the tested network elements that ACS 5.8 supports.
CoA Support
ACS supports Change of Authorization (CoA) on the Cisco IOS version 12.2(52)SE. Table 2 lists the devices and images that support CoA:
Supported External Identity Stores
ACS 5.8 supports the following external identity stores:
■Lightweight Directory Access Protocol Server
Lightweight Directory Access Protocol Server
ACS 5.8 supports Lightweight Directory Access Protocol (LDAP) servers. The supported LDAP servers include, but are not limited to:
■SunONE LDAP Directory Server - Version 5.5
Supported 802.1X Clients
ACS 5.8 supports all 802.1X clients. These include, but are not limited to:
■Microsoft Built-In Windows Vista 802.1X Client
■Microsoft Built-In Windows 7 802.1X Client
■Microsoft Built-In Windows 8 802.1X Client
■Microsoft Built-In Windows 8.1 802.1X Client
■Microsoft Built-In Windows 8.1 update 2 802.1X Client
■Microsoft Built-In Windows 10 802.1X Client
Supported Remote Repositories
ACS 5.8 supports the following remote repositories:
■cdrom—Local (CD-ROM) Drive (read only)
■http—URL using a HTTP server (read only)
Supported Browsers
ACS 5.8 supports the following browser platforms:
–Mozilla Firefox version 38.2.0 ESR
–Mozilla Firefox version 45.0.2 ESR
■Windows 7 32-bit and 7 64-bit
–Internet Explorer version 11.x
–Mozilla Firefox version 38.1.0 ESR
–Mozilla Firefox version 38.2.0 ESR
–Mozilla Firefox version 45.0.2 ESR
–Internet Explorer version 11.x
–Mozilla Firefox version 38.2.0 ESR
–Mozilla Firefox version 45.0.2 ESR
Note: Mozilla Firefox version 46.x or later is supported only after installing ACS 5.8 patch 3 or later.
Note: You can launch the ACS web interface using IPv6 addresses only in Internet Explorer 7.x or later and Mozilla Firefox 3.x versions.
Supported Authentication Protocols
ACS 5.8 supports the following protocols:
■PEAP (with inner EAP-MSCHAPv2/EAP-GTC/EAP-TLS)
SNMP Support
ACS 5.8 supports Simple Network Management Protocol (SNMP) to provide logging services. The SNMP agent provides read-only SNMPv1 and SNMPv2c support. The supported MIBs include:
Syslog Support
ACS 5.8 conforms to syslog standards (RFC 3164 and RFC 5424) and supports any generic syslog server. In addition, ACS supports the following:
■Syslog over TCP and UDP follows the standards of RFC 6587.
■Syslog over TLS (Secure TCP and UDP) follows the standards of RFC 5425.
Supported VMware Versions
ACS 5.8 can be installed on the VMware ESXi 5.5; ESXi 5.5 update 1, update 2, and update 3; and ESXi 6.0 update 2 versions.
For information on the VMware machine requirements and installation procedures, refer to Installing ACS in a VMware Virtual Machine chapter in the Installation and Upgrade Guide for Cisco Secure Access Control System 5.8.
Related Documentation
Note: The printed and electronic documentation is sometimes updated after original publication. Therefore, you should also review the documentation on http://www.cisco.com for any updates.
Table 4 lists the product documentation that is available for ACS 5.8. To find end-user documentation for all the products on Cisco.com, go to: http://www.cisco.com/go/techdocs
Select Products > Security > Access Control and Policy > Policy and Access Management > Cisco Secure Access Control System.
Notices
The following notices pertain to this software license.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit ( http://www.openssl.org/).
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
This product includes software written by Tim Hudson (tjh@cryptsoft.com).
The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.
Copyright © 1998-2007 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgment: “This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit ( http://www.openssl.org/)”.
4. The names “OpenSSL Toolkit” and “OpenSSL Project” must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.
5. Products derived from this software may not be called “OpenSSL” nor may “OpenSSL” appear in their names without prior written permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment:
“This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit ( http://www.openssl.org/)”.
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT “AS IS”' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).
Copyright © 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.
This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).
The implementation was written so as to conform with Netscapes SSL.
This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).
Copyright remains Eric Young’s, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgement:
“This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)”.
The word ‘cryptographic’ can be left out if the routines from the library being used are not cryptography-related.
4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: “This product includes software written by Tim Hudson (tjh@cryptsoft.com)”.
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License].
Obtain Documentation and Submit a Service Request
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation.
To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What’s New in Cisco Product Documentation RSS feed. The RSS feeds are a free service.
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)
Feedback