Guest

Cisco Secure Access Control System

Supported and Interoperable Devices and Software Tables for the Cisco Secure Access Control System 5.0

  • Viewing Options

  • PDF (142.3 KB)
  • Feedback
Supported and Interoperable Devices and Software Tables for the Cisco Secure Access Control System 5.0

Table Of Contents

Supported and Interoperable Devices and Software Tables for the Cisco Secure Access Control System 5.0

Supported Devices

RADIUS and TACACS+

Supported User Repositories

Windows Active Directory

Lightweight Directory Access Protocol Server

Supported 802.1x Clients

Supported Web Client/Browser Platforms

Supported Protocols

SNMP Support

Syslog Support

Documentation Updates

Notices

OpenSSL/Open SSL Project

License Issues

Obtaining Documentation and Submitting a Service Request


Supported and Interoperable Devices and Software Tables for the Cisco Secure Access Control System 5.0


Revised: December 31, 2010

The Cisco Secure Access Control System Release 5.0, hereafter referred to as ACS, works with hundreds of devices. You can use this document to find devices and software that ACS 5.0 supports.

For details regarding limitations and known problems, see the Release Notes for the Cisco Secure Access Control System 5.0.

This document contains:

Supported Devices

Supported User Repositories

Supported 802.1x Clients

Supported Web Client/Browser Platforms

Supported Protocols

SNMP Support

Syslog Support

Documentation Updates

Notices

Obtaining Documentation and Submitting a Service Request

Supported Devices

ACS 5.0 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 2138Remote Authentication Dial In User Service (RADIUS)

RFC 2139RADIUS Accounting

RFC 2865Remote Authentication Dial In User Service (RADIUS)

RFC 2866RADIUS Accounting

RFC 2867RADIUS Accounting for Tunnel Protocol Support

RFC 2868RADIUS Attributes for Tunnel Protocol Support

RFC 2869RADIUS Extensions


Note For details regarding the implementation of vendor-specific attributes (VSAs), see the User Guide for the Cisco Secure Access Control System 5.0.


The supported devices include but are not limited to the Tested Network Elements listed in Table 1.

Table 1 lists some of the Tested Network Elements that ACS 5.0 supports.

Table 1 Tested Network Elements 

Network Elements
Operating System with Version

Cisco 2610

IOS 12.3.17b

Cisco 3640

IOS 12.3.17b

Cisco 7200

IOS 12.3.17b

Cisco 3750

IOS 12.2(25r)

Catalyst WS-3560-24TS Switch

IOS 12.2(25)-SEC2

Cisco 515E PIX

PIX OS 6.3.5

Cisco AP 1200

IOS 12.3(7)JA1

Nexus 7000

4.0(4)

Catalyst 6000

12.2 (SIERRA_INTEG_080914)

IP Phone

Cisco IP Phone 7970


Supported User Repositories

ACS 5.0 supports the following external user repositories:

Windows Active Directory

Lightweight Directory Access Protocol Server

Windows Active Directory

ACS 5.0 supports all editions of:

Windows Active Directory (AD) 2000

Windows AD 2003

Windows AD 2008

Lightweight Directory Access Protocol Server

ACS 5.0 supports Lightweight Directory Access Protocol (LDAP) servers. The supported LDAP servers include but are not limited to:

SunONE LDAP Directory Server - Version 5.2

Linux LDAP Directory Server - Version 4.1

Open LDAP Directory Server

Supported 802.1x Clients

ACS 5.0 supports all 802.1x clients. These include but are not limited to:

Microsoft Built-In Windows XP 802.1x Client

Microsoft Built-In Windows Vista 802.1x Client

CSSC version 4.x

CSSC version 5.x

Juniper-Odyssey (latest version)

Supported Web Client/Browser Platforms

Windows XP (Service Pack 2) and Windows Vista

Internet Explorer version 6.x

Internet Explorer version 7.x

Mozilla Firefox version 2.x only (not higher)

MAC OS 10.5

Mozilla Firefox version 2.x only (not higher)

Supported Protocols

ACS 5.0 supports the following protocols:

PAP/ASCII

EAP-MD5

EAP-TLS

PEAP[MSCHAPv2]

EAP-FAST[MSCHAPv2]

SNMP Support

ACS 5.0 supports Simple Network Management Protocol (SNMP) to provide logging services.. The SNMP agent provides read-only SNMP v1 and SNMP v2c support. The supported Management Information Bases (MIBs) include:

SNMPv2-MIB

RFC1213-MIB (MIB II)

IF-MIB

IP-MIB

TCP-MIB

UDP-MIB

ENTITY-MIB

The SNMP agent is configurable on the appliance configuration page.

Syslog Support

ACS 5.0 supports all syslog servers.

Documentation Updates

Table 2 Updates to the Supported and Interoperable Devices and Softwares for the Cisco Secure Access Control System 5.0

Date
Description

12/31/2010

Removed HOST-RESOURCES MIB from the list of supported MIBs, according to the CSCtl21755.


Notices

The following notices pertain to this software license.

OpenSSL/Open SSL Project

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).

License Issues

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.

OpenSSL License:

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).

Original SSLeay License:

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].

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:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (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.