Release Notes for Cisco Secure Access Control Server for Windows 2000/NT Servers Version 3.0.3

These release notes pertain to Cisco Secure Access Control Server for Windows 2000/NT Servers (Cisco Secure ACS) version 3.0.3.

Introduction

Cisco Secure ACS provides authentication, authorization, and accounting (AAA—pronounced "triple A") services to network devices that function as AAA clients, such as a network access server, PIX Firewall, or router. A AAA client is any such device that provides AAA client functionality and uses one of the AAA protocols supported by Cisco Secure ACS.

Cisco Secure ACS helps centralize access control and accounting, in addition to router and switch access management. With Cisco Secure ACS, network administrators can quickly administer accounts and globally change levels of service offerings for entire groups of users. Although using an external user database is optional, Cisco Secure ACS supports many popular user databases, enabling companies to use the knowledge gained from and the investment already made in building their corporate user databases.

Cisco Secure ACS supports Cisco AAA clients such as the Cisco 2509, 2511, 3620, 3640, AS5200 and AS5300, AS5800, the Cisco PIX Firewall, Cisco Aironet Access Point wireless networking devices, Cisco VPN 3000-series Concentrators, and Cisco VPN 5000-series Concentrators. It also supports third-party devices that can be configured with Terminal Access Controller Access Control System (TACACS+) or Remote Access Dial-In User Service (RADIUS) protocols. Cisco Secure ACS treats all such devices as AAA clients. Cisco Secure ACS uses the TACACS+ and RADIUS protocols to provide AAA services that ensure a secure environment. For more information about support for TACACS+ and RADIUS in Cisco Secure ACS, see the Cisco Secure ACS for Windows 2000/NT Servers User Guide.

Installing Cisco Secure ACS 3.0 for Windows 2000/NT Servers provides information about the following subjects:

System requirements
Network requirements

Cisco Secure ACS for Windows 2000/NT Servers User Guide provides detailed information about configuring and using Cisco Secure ACS. This guide is available from Cisco.com or on the product CD.

New Features

Major Features

802.1x Support—Cisco Secure ACS support for 802.1x strengthens access control for switched LAN and wireless LAN users. 802.1x is a new access control standard proposed by the IEEE for managing port-level access control. 802.1x relies on Extensible Authentication Protocol (EAP), carried in RADIUS messages, to manage user authentication and authorization.
EAP-MD5, EAP-TLS—In addition to supporting LEAP, Cisco Secure ACS supports EAP-MD5 and EAP-TLS authentication. EAP is an IETF RFC standard for carrying various authentication methods over any PPP connection. EAP-MD5 is a username and password method incorporating MD5 hashing for security. EAP-TLS is a method for authenticating both Cisco Secure ACS and users with X.509 digital certificates. This method also provides dynamic session key negotiation.
Command Authorization Sets—Command authorization sets provide a centralized mechanism to manage TACACS+ administrative control. Driven by some of the largest enterprise and service provider networks that use Cisco Secure ACS, command authorization sets provide a method to group and name device command profiles that can be paired with users, groups of users, or network device groups. A key benefit of command authorization sets is the ability to remove any requirement of individual privilege level or command restrictions on each AAA client. This feature greatly enhances the scalability and manageability of setting device command authorization restrictions for network administrators.
MS CHAP version 2 Support and MS CHAP Password Aging Support—Cisco Secure ACS supports MS CHAP version 2. In addition, we added an MS CHAP-based password-aging feature which works with the Microsoft Dial-Up Networking client, the Cisco VPN client (version 3.0 or greater), and any desktop client that supports MS CHAP. This feature prompts a user to change his or her password after a login where the user password has expired. The MS CHAP-based password-aging feature supports users who authenticate with a Windows user database and is offered in addition to password aging supported by the CiscoSecure user database.

Minor Features

Per-User Access Control Lists (ACLs)—This feature allows administrators to define ACLs of any length for users or groups of users.
Shared Network Access Restrictions (NARs)—The ability to name NARs simplifies the assignment of identical NARs to multiple users or groups of users.
Wildcards in NARs—Cisco Secure ACS supports wildcards for designating end-user client IP addresses and ports in IP-based NARs. In CLI/DNIS-based NARs, Cisco Secure ACS supports wildcards for CLI and DNIS values. You can apply NARs to a single AAA client, a network device group, or all AAA clients. Wildcarding of AAA clients is supported by using the multiple devices per AAA client feature, described next.
Multiple Devices per AAA Client Configuration—You can create single AAA client configurations that define a set of network devices that use the same shared key, authentication method, and logging/accounting parameters. Cisco Secure ACS enables you to provide multiple IP addresses, including the use of wildcards in IP addresses, when you configure a AAA client in the HTML interface.
Multiple LDAP Lookups and LDAP Failover—Cisco Secure ACS enables you to create multiple LDAP external user database configurations. You can also define backup LDAP servers for use if a primary LDAP server is not available.
User-Defined RADIUS Vendor-Specific Attributes (VSAs)—Cisco Secure ACS now supports user-defined inbound and outbound RADIUS VSAs.
Improved User Documentation—We reorganized and heavily revised the online documentation and Cisco Secure ACS for Windows 2000/NT Servers Version 3.0 User Guide. We rewrote and expanded Installing Cisco Secure ACS 3.0 for Windows 2000/NT Servers. We heavily revised Web Server Installation for Cisco Secure ACS 3.0 for Windows 2000/NT User-Changeable Passwords.

To supplement the documentation, white papers about using and deploying various protocols and AAA clients are posted at the following URL:

Installation Notes

For information about installing Cisco Secure ACS, see Installing Cisco Secure ACS 3.0 for Windows 2000/NT Servers.

Changes to CRYPTOCard Support

Before Cisco Secure ACS 3.0.1, support for CRYPTOCard token servers used the vendor-proprietary interface provided with the CRYPTOCard token server. Beginning with Cisco Secure ACS 3.0.1, we support CRYPTOCard token servers using a standard RADIUS interface.

If you upgrade to Cisco Secure ACS 3.0 and had configured CRYPTOCard authentication in the previous installation of Cisco Secure ACS, the installation program prompts you for information about the CRYPTOCard RADIUS server. With this information, the installation program replaces the older CRYPTOCard configuration with a new one that uses the RADIUS interface of the CRYTPOCard easyRADIUS server. To use the RADIUS interface of the CRYPTOCard server, be sure the CRYPTOCard easyRADIUS server is installed on a CRYPTOCard Windows server. For more information about CRYPTOCard easyRADIUS, see CRYPTOCard documentation.

We successfully tested running Cisco Secure ACS and the CRYPTOCard easyRADIUS server on the same Windows server. Testing occurred on Windows NT 4.0 with Service Pack 6 and Windows 2000 with Service Pack 2. We used CRYPTOCard easyRADIUS server versions 5.0 and 5.1. However, we recommend that you do not run the CRYPTOCard easyRADIUS server on the same Windows server that runs Cisco Secure ACS. If you choose to do so, be sure that Cisco Secure ACS and CRYPTOCard easyRADIUS use different ports to receive RADIUS requests.

You can change the UDP ports used by the CRYPTOCard RADIUS server by editing its services file, usually located in c:\WINNT\system32\drivers\etc. For more information about the UDP ports used by the CRYPTOCard RADIUS server and how to change them, see your CRYPTOCard documentation.

Evaluation Version

The evaluation version of Cisco Secure ACS 3.0 provides full functionality for 90 days after the date of installation. This allows you to use all features of Cisco Secure ACS 3.0 while determining if it meets your needs. The evaluation version of Cisco Secure ACS 3.0 will be available 30 days after the release of the commercial version of Cisco Secure ACS 3.0.

You can distinguish the evaluation version of Cisco Secure ACS 3.0 from the commercial version in the following ways:

The word "trial" appears in the title of the installation routine.
The Windows Control Panel Add/Remove applet indicates that the Cisco Secure ACS installation is a trial version.
In the administrative interface of Cisco Secure ACS, the word "trial" appears on the title of the initial screen.

When the evaluation period has elapsed, the CSRadius and CSTacacs services fail to start. You will receive a message upon accessing the administrative interface notifying you that your evaluation period has elapsed.

Purchasing the Commercial Version

Please contact your Cisco Sales Representative(s) to inquire about purchasing the commercial version of Cisco Secure ACS. To purchase the commercial version of Cisco Secure ACS 3.0 online, use Part Number CSACS-3.0 at the following URL:

Upgrading to the Commercial Version

After purchasing a commercial version of Cisco Secure ACS 3.0, you can upgrade your Cisco Secure ACS server from the evaluation version to the commercial version by installing the commercial version over the evaluation version. For information on installing Cisco Secure ACS 3.0, follow the instructions in Installing Cisco Secure ACS 3.0 for Windows 2000/NT Servers.

Limitations and Restrictions

The following topics are limitations and restrictions that apply to Cisco Secure ACS 3.0.3.

Interoperability Testing

Cisco Secure ACS has not been interoperability tested with other Cisco software. Other than for the software and operating system versions listed in this document, we performed no interoperability testing. Using untested software with Cisco Secure ACS may cause undesired results. For the best performance of Cisco Secure ACS, we recommend that you use the versions of software and operating systems listed in this document.

Upgrade Testing

Tested Certificate Servers

Tested Web Browser Versions

To administer all features included in Cisco Secure ACS 3.0, we recommend that you use one of the following tested web browsers:

Microsoft Internet Explorer version 6.0 for Microsoft Windows
Netscape Communicator version 7.0 for Microsoft Windows

We did not test other versions of these browsers, nor did we test web browsers by other manufacturers.

Tested Token Servers

Because we made no changes to token support, we did not conduct token server testing with Cisco Secure ACS version 3.0.3. We tested Cisco Secure ACS version 3.0.2 with the following token server software:

PassGo (formerly AXENT) Defender version 4.1.3
Secure Computing SafeWord version 5.2
RSA ACE/Server version 5.0 and ACE/Client version 1.1.2 for Windows 2000
ActivCard Server 3.1
Vasco Vacman Server 6.0.2

Note Cisco Secure ACS 3.0.2 supports CRYPTOCard, ActivCard, and Vasco token servers using RADIUS.

Tested LDAP Server

We used Netscape iPlanet Directory Server version 5.1 and Windows 2000 Active Directory with Windows Service Pack 3 to test standard LDAP database support.

Tested Novell NDS and Novell Clients

Because we made no changes to Novell support, we did not conduct Novell testing with Cisco Secure ACS version 3.0.3. We tested Cisco Secure ACS version 3.0.2 with the following Novell software:

We used Netware 6.0 to test Novell NDS external user databases.
We tested Cisco Secure ACS 3.0.2 with the Novell Requestor software found in Novell Client version 4.8.3 for Windows NT/2000. To authenticate users with a Novell NDS external user database, the Novell Requestor software must be installed on the Windows server that runs Cisco Secure ACS.

Tested Windows 2000 Service Packs

We used Windows 2000 with Service Pack 3 and Windows NT 4.0 with Service Pack 6 to test Cisco Secure ACS version 3.0.3 for Windows authentication.

Tested Platforms for CiscoSecure Authentication Agent

Because we made no changes to CiscoSecure Authentication Agent support, we did not conduct CiscoSecure Authentication Agent testing with Cisco Secure ACS version 3.0.3. With Cisco Secure ACS 3.0.2, we tested CiscoSecure Authentication Agent on the following client platform operating systems:

Windows 98
Windows 2000

We did not test the CiscoSecure Authentication Agent on the following client platform operating systems:

Windows 95
Windows NT 4.0

Caveats

Platform Caveats

Refer to the appropriate release notes for information about hardware caveats that might affect Cisco Secure ACS. You can access these release notes online at the following URLs.

Cisco Secure PIX Firewall

Cisco IOS

Cisco VPN 3000 Concentrator

Cisco VPN 5000 Concentrator

Cisco Aironet Access Point

Cisco Catalyst Switches

Resolved Caveats—Version 3.0.3

CSCdw79587: Bad TACACS+ Authorization packets cause CSLOG to spin
CSCdy50194: Restart condition for CSMon
CSCdy65011: CSauth lockup during replication
CSCdy83340: enhancement request:CSDBsync -r should restore more info
CSCdy83399: Cannot restore 3.0(1) backup into 3.0(2)
CSCdz44076: CSRadius preventing wlan APs failing over

Open Caveats—Version 3.0.3

CSCds14916: ACS fails to list Windows NT groups when PDC is down

If the active Primary Domain Controller (PDC) for a Windows NT domain is unavailable, you cannot use the Cisco Secure ACS administrative user interface to configure group mappings for this domain.

Workaround/Solution: If the configuration changes are not vital, wait until the PDC becomes available again. Otherwise, promote a suitable Backup Domain Controller to the role of PDC.

CSCds44804: Windows 2000-style user@domain authentication not supported

Windows 2000 allows users to enter their user names as username@domain-name. For example, fred@domain.com. This format is equivalent to entering the Windows NT 4.0 user name of DOMAIN/fred.

Workaround/Solution: Cisco Secure ACS does not support this style of user name when authenticating against an external Windows 2000 server. Continue to prefix account names with the NT 4.0-style domain name.

CSCds48020: Installation GUI Before You Begin check boxes are unclear

On the Before You Begin dialog box of the Cisco Secure ACS installation, the following three check box items could be misunderstood.

A dial-up client can successfully dial in to the network access server.
The network access server is running Cisco IOS release 11.1 or later.
Microsoft Internet Explorer v5.0 (or later) or Netscape Communicator v4.7 (or later) is installed on this Windows 2000/NT Server

Dial-up clients only need to be able to connect to your network if you intend to support dial-up access. If not, this is not a requirement for installing Cisco Secure ACS.
Only Cisco IOS devices need to be running Cisco IOS release 11.1 or later. Other devices, such as supported versions of the Cisco Aironet Access Point, do not need to be running Cisco IOS.
The supported web browsers must also have a Java virtual machine installed in order to support the Cisco Secure ACS administration interface.

CSCds90678: Failed to Edit TACACS+ (Cisco IOS) configuration

If you use Internet Explorer 5.5 or Netscape 4.7 and refresh or reload the frame when viewing Interface Configuration: TACACS+(Cisco IOS), you receive the following error message:

Workaround/Solution: Click Interface Configuration: TACACS+(Cisco IOS) and continue editing the TACACS+ settings.

In Cisco Secure ACS 3.0, this behavior does not occur with Internet Explorer 5.5.

CSCdu33140: PPTP Tunnel with VPN3000 and MS-CHAP V2 method

A PPTP tunnel using a Cisco VPN 3000-series concentrator and MS-CHAP version 2 fails. The VPN concentrator indicates that authentication passed; however, tunnel establishment fails. When using the MS-CHAP version 1 method with the same configuration, tunnel establishment succeeds. When using the concentrator's internal user database with MS-CHAP version 2, tunnel establishment succeeds.

Workaround/Solution: There are few steps which needs to be filled when configuring Cisco Secure ACS to support PPTP Tunnel in MS-CHAP version 2 (and version 1) authentication methods:

Setup two users at least on Cisco Secure ACS, one as a tunnel user and the others as the authenticated users. The tunnel user and its password should be the same as the tunnel group name on the concentrator and its password.

The authenticated users must include the following settings in Cisco Secure ACS, as well:

In "IETF RADIUS Attributes" check the "[025] Class" attribute and the following value should be entered in the text box: "ou=groupname;" where groupname is the name of the tunnel user name previously configured.
In "Microsoft RADIUS Attributes", select the "[311\012] MS-CHAP-MPPE-Keys" check box.
Add a group name similar to the tunnel users name, and in the "Cisco VPN 3000 Concentrator RADIUS Attributes" select the [3076\011] CVPN3000-Tunneling-Protocols check box and the [3076\020] CVPN3000-PPTP-Encryption check box.
Select the [3076\011] CVPN3000-Tunneling-Protocols check box, then select PPTP from the corresponding list.
Select the [3076\020] CVPN3000-PPTP-Encryption check box, then select 128-bit or lower from the corresponding list, according to the client encryption capability

Use the Windows 2000 PPTP client and establish the PPTP tunnel via MS-CHAP V2 authentication method.

CSCdu40827: Passwords submitted with Netscape on Solaris dont work

Workaround/Solution: Use a Windows version of the web browsers used to test Cisco Secure ACS.

CSCdu48120: CSNT error occurred during the move data process

Workaround/Solution: Delete pdh.dll from the Windows system32 directory, then restart the installation.

CSCdu76831: 255 IP address fails on installation

During installation, if you use an IP address of 10.0.10.255 with a 23-bit subnet mask (255.254.0.0), the installation fails with an error message indicating that you cannot use a broadcast IP address.

Workaround/Solution: During installation, enter any IP address not ending in 255. After installation, use the Cisco Secure ACS HTML interface to correct the IP address.

CSCdu84042: Win2k external database,W2K groups cant be seen

Windows 2000 groups for remote domains cannot be seen by Cisco Secure ACS running on a Windows NT 4.0 member server.

Workaround/Solution: On the Cisco Secure ACS server, configure all Cisco Secure ACS services to run using a domain administrator account for the domain of which the server is a member. For more information about additional configuration required to run Cisco Secure ACS 3.0 on a Windows NT 4.0 member server, see Installing Cisco Secure ACS 3.0 for Windows 2000/NT Servers.

CSAdmin
CSAuth
CSDBSync
CSLog
CSMon
CSTacacs
CSRadius

CSCdv29929: Add admin using Netscape causes 100%CPU

If you use Netscape Navigator v.4.7 to access the HTML interface, adding an administrator to Cisco Secure ACS can cause 100% CPU utilization for over a minute. This in turn can cause the CSRadius service to pause until the browser resumes normal operation. The fault lies in the Netscape browser rather than Cisco Secure ACS.

Workaround/Solution: Once the 100% CPU utilization has begun, wait until browser operation returns to normal. This should be less than five minutes. To avoid the behavior altogether, use a tested version of Microsoft Internet Explorer. See the Tested Web Browsers section of the Release Notes for Cisco Secure Access Control Server for Windows 2000/NT Servers

CSCdv35872: Insufficient length for NDS context entry

When a Novell NDS database configuration in Cisco Secure ACS has a context list greater than 4095 characters long, editing the NDS configuration page results in incorrect HTMLin the browser interface.

CSCdv47186: Unable to add renamed user-defined attributes ito Radius accounting

Customer is experiencing problems adding the user fields (3,4,5) to the RADIUS accounting file.

When he renames these fields in the User Attributes in Interface Configuration, and then attempts to add them to the RADIUS Accounting log, the changes do not appear in the log.

1. Change the names of Real Name, User field 2, User field 3, or any of the User Defined Fields in Interface Configuration.

2. In System Configuration, select Logging, and then select CSV Radius Accounting.

6. The field you just moved to the right column will no longer be in the right column, but will appear in the left column once more.

Workaround/Solution: After renaming a user-defined attribute, restart all Cisco Secure ACS services from the Windows Control Panel. Once the services have been restarted, the CSV RADIUS Accounting configuration screen shows the renamed attributes and remembers their selection when the page is submitted.

CSCdv85400: IP Address Recovery & Date Format Control - not backup/restore

In the System Configuration section, settings made on the IP Address Recovery page and the Date Format Control page are not restored from backup.

Workaround/Solution: Manually configure the IP Address Recovery and Date Format Control pages.

CSCdv85432: CSLog crashes when changing system logging

The CSLog service crashes when you modify ODBC logging configuration during ODBC logging operations.

Workaround/Solution: Do not change logging configuration while Cisco Secure ACS is authenticating users.

CSCdv86707: User Data Field name is not replicated

Changes to user-defined fields in user records do not appear to replicate. After the user-defined fields are changed in the Interface Configuration section on the primary Cisco Secure ACS server and replication succeeds, the secondary Cisco Secure ACS server does not display the changes to the user-defined fields in the HTML interface.

Workaround/Solution: The changes to the user-defined fields do replicate successfully; however, to see the changes on the secondary Cisco Secure ACS server, restart the CSAdmin service.

CSCdv86708: HTTP Port Allocation is not replicated

Changes to HTTP Port Allocation settings do not appear to replicate. After the HTTP Port Allocation settings are changed on the Access Policy Setup page in the Administration Control section on the primary Cisco Secure ACS server and replication succeeds, the secondary Cisco Secure ACS server does not display the changes to the HTTP Port Allocation settings in the HTML interface.

Workaround/Solution: The changes to the HTTP Port Allocation settings do replicate successfully; however, to see the changes on the secondary Cisco Secure ACS server, restart the CSAdmin service.

CSCdv89331: VOIP Accounting Configuration - no upgrade, no backup & restore

In the System Configuration section, settings made on the VoIP Account Configuration page are not restored from backup. Neither are these settings preserved during reinstallation of Cisco Secure ACS 3.0 or upgrading to a later build of Cisco Secure ACS 3.0.

CSCdw19491: Unable to add renamed user-defined attributes ito Radius accounting

Customer is experiencing problems adding the user fields (3,4,5) to the RADIUS accounting file. When he renames these fields in the User Attributes in Interface Configuration, and then attempts to add them to the RADIUS Accounting log, the changes do not appear in the log.

1. Change the names of Real Name, User field 2, User field 3, or any of the User Defined Fields in Interface Configuration.

2. In System Configuration, select Logging, and then select CSV Radius Accounting.

6. The field you just moved to the right column will no longer be in the right column, but will appear in the left column once more.

Workaround/Solution: After renaming a user-defined attribute, restart all Cisco Secure ACS services from the Windows Control Panel.

Once the services have been restarted, the CSV RADIUS Accounting configuration screen shows the renamed attributes and remembers their selection when the page is submitted.

CSCdw27562: AAA Servers not deleted if Sync Partners table is empty

An AAA server cannot be deleted from the "(Not Assigned) AAA Servers" table if the "Synchronize" table in the "Synchronization Partners" is empty. An error message "x.x.x.x can not be deleted since it is an synchronization partner" is displayed.

Workaround/Solution: Move any AAA server to the Synchronize table, then delete the desired AAA server.

CSCdx15245: Database replication partner order not saved

Changes to the order of the Replication Partners, under Database Replication is not saved when submitting changes. When you get into the Database Replication window, the servers are shown in alphabetical order and not in the order desired. The database replication is also done in alphabetical order, so in the order shown by the GUI after submitting changes.

CSCdx48265: Character in hostname crashes ACS

CSCdx51442: cmd-agr=permit 0 in Command Author Set allows all arguments

After setting up command Authorization Sets in ACS 3.0, and specifying authorization for config-commands in NAS. Customer specifies to permit cmd=interface cmd-arg=permit FastEthernet 0

Issuing this config command fails as it expect the "0" as a separate argument. But after adding a cmd-arg="permit 0" all interface commands are allowed - not just on FastEthernet.

CSCdx73692: csradius and cstacacs crash with safeword users on unix box

Authentication services CSRadius and CSTacacs might crash when ACS 2.6.3.2 is installed on windows 2000 with service pack 1 and when safeword is used on a separate unix box. All users are safeword users.

Workaround/Solution: None at this time. We tested Cisco Secure ACS 3.0 on Windows 2000 Server using an English-language version of Service Pack 2. Apply Service Pack 2 may alleviate the issue.

CSCdx81906: Unable to replicate to more than 20 partners

Customer has run into a limitation on replication partners of 20. You can configure more, but the 21st partner in the list but it will not work - the master will say that it's not responding.

Workaround/Solution: If you delete one of the servers higher up in the list, thus moving the problem server into slot number 20, replication works.

CSCdx89261: unable to delete NAS

CSCdy02612: DCS assignment policy per NDG works incorrectly

Command authorization appears to fail on all AAA clients when the applicable command authorization set is configured to be applied to the <Default> network device group (NDG).

This is correct behavior. The <Default> NDG corresponds to the "Not Assigned" NDG in Network Configuration. If the AAA client on which the user is attempting to issue commands is not in the "Not Assigned" NDG and there is no command authorization set that does apply to the AAA client, Cisco Secure ACS denies authorization for the command.

Workaround/Solution: If you intend to apply a command authorization set to all AAA clients, assign it once per every NDG rather than solely to the <Default> NDG. There is currently no single option that applies a command authorization set to all NDGs.

CSCdy07147: EAP-MD5 Fails when RADIUS (Cisco Aironet) as authenticator

EAP-MD5 Authentication fails when AAA Client use RADIUS (Cisco Aironet) as an authentication method.

Workaround/Solution: When RADIUS (IETF) is being used EAP-MD5 authentication operates properly.

CSCdy11863: Invalid PIX ACL is accepted

Cisco Secure ACS accepts empty and therefore invalid PIX ACLs. There are two ways this can occur. In the first, you can submit only a space in the PIX ACL. In the second, you can delete the contents of a previously submitted, valid PIX ACL and resubmit it successfully.

CSCdy14259: T+ ascii login doesn't work correctly with cryptocard

Users authenticating with CryptoCard incorrectly receive a password prompt in addition to the username, challenge, and response prompts.

Workaround/Solution: Users can enter any string at the password prompt and press Enter, then continue CryptoCard authentication normally.

CSCdy15221: LDAP Group mapping disappears

CSCdz10935: previous button disappears on use setup page of ACS

The "Previous" button disappears when using the User Setup page in the Cisco Secure ACS HTML interface.

CSCdz27070: disc-cause attribute is wrong in Tacacs+ Acct logs

Cisco Secure ACS 2.6.4, 3.0.2, and 3.1.1 all log an incorrect value in TACACS+ Accounting for the "disc-cause" attribute. If you set up a PPP session to do an idle timeout, when it disconnects you will get "CLID-Authentication-Failure" in the TACACS+ Accounting log for "disc-cause" - but the TACACS+ documentation for IOS says that the value "4" is Idle timeout.

CSCdz32794: wireless client cannot EAP login when max session limit is 1

Aironet wireless client cannot LEAP login when "MAX sessions" set to limit 1 user.

CSCdz34158: resume install ends in err on not found files

While upgrading from Cisco Secure ACS 3.0.2.5 to 3.0.3, if you cancel the upgrade at the dialog box that presents the options to keep or delete the existing database and then continue the upgrade by clicking Resume, you receive an error message for each Cisco Secure ACS service that the service cannot be found. Upgrade cannot be resumed.

Workaround/Solution: Use the clean.exe application for 3.0.3 to remove Cisco Secure ACS, reinstall 3.0, restore Cisco Secure ACS configuration from the most recent backup file, and upgrade again without attempting to cancel the upgrade.

CSCdz35833: Clean doesn't clean/recognize all entries

If you attempt to upgrade to Cisco Secure ACS 3.0.3 from 3.0.2.5 and abort installation of 3.0.3 before it is complete, using the clean.exe application that comes with 3.0.2.5 does not remove all related file system directories or registry keys.

Workaround/Solution: Manually edit the registry to remove HKLM:SOFTWARE/Cisco/CiscoAAAv3.0 entries. Manually delete remaining Cisco Secure ACS 3.0 subdirectories.

CSCdz37379: Replication pre-checks incorrect in cascade

Occasionally updated components are not replicated to the third replication partner in a replication cascade. This happens because replication pre-checks on the second partner indicate incorrectly that outbound replication is not required for the third partner in the cascade. This occurs because the pre-checks performed by the second replication partner happen before replication is completed from the first replication partner.

Workaround/Solution: On the following replication cycle, the unreplicated component will be replicated from the second replication partner to the third replication partner.

CSCdz42735: version 2.6 in clean of 3.0.3.3 dialogs

The initial dialog box encountered in the clean.exe application distributed with Cisco Secure ACS version 3.0.3 incorrectly says that it is for version 2.6.

CSCdz43939: change password fail in err709.In Auth log-err 1907L

This behavior occurs after upgrading Cisco Secure ACS from 3.0.2.5 to 3.0.3 and when Cisco Secure ACS is running on a member server. Users whose accounts reside in a Windows 2000 user database and whose accounts are configured to enforce a password change at next login are disconnected after providing the new password.

CSCdz45040: Password change for native trusted domain doesn't work

When Cisco Secure ACS authenticates a Windows 2000 user from native trusted domain, MS-CHAP password changing doesn't work even though authentication via MS-CHAPv2 works properly.

CSCdz45527: EAP-TLS fails to initiate after restore process

EAP-TLS Authentication fails after successful Restore process. Seems that the problem is related to Private Keys decryption failing after restore. The following error is presented in CSAuth log after a successful restore process:

The problem occurs when using restore from a dump file created during backup on other machine.

It also occurs when the dump file was backed up, ACS was uninstalled and then Installed and restored from a dump file.

Table of Contents