Table of ContentsRelease Notes for Cisco Secure Access Control Server for Windows 2000/NT Servers Version 3.0.4
Changes to CRYPTOCard Support
Limitations and Restrictions
Tested Certificate Servers
Tested Web Browser Versions
Tested Token Servers
Tested LDAP Server
Tested Novell NDS and Novell Clients
Tested Windows 2000 Service Packs
Tested Platforms for CiscoSecure Authentication Agent
Cisco VPN 3000 Concentrator
Cisco VPN 5000 Concentrator
Cisco Aironet Access Point
Cisco Catalyst Switches
Resolved Caveats—Version 3.0.3
Resolved Caveats—Version 3.0.2
Resolved Caveats—Version 3.0.1
Open Caveats—Version 3.0.4
Obtaining Technical Assistance
Obtaining Additional Publications and Information
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.
- 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.
|Note Cisco VPN 3000-series Concentrators and Cisco IOS will support MS CHAP password aging in upcoming releases.|
- 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.
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 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.
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.
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.
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:
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.
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.
To administer all features included in Cisco Secure ACS 3.0.4, we recommend that you use the English-language edition of Microsoft Internet Explorer version 6.0 SP1 for Microsoft Windows. For previous releases of Cisco Secure ACS 3.0, we also tested Netscape Communicator version 7.0 for Microsoft Windows; however we tested Cisco Secure ACS 3.0.4 solely with Microsoft Internet Explorer.
|Note To use a web browser to access the Cisco Secure ACS HTML interface, configure your web browser as follows:|
- 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.|
For information about CRYPTOCard support, see Changes to CRYPTOCard Support.
- 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.
|Note Cisco Secure ACS only supports English language versions of Windows and its Service Packs.|
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.4. With Cisco Secure ACS 3.0.2, we tested CiscoSecure Authentication Agent on the following client platform operating systems:
|Note Caveats are printed word-for-word as they appear in our caveat tracking system.|
- CSCdy00184: Change behaviour for times out pause notifications for CSMon
- CSCdz67212: Incorrect reply message length is set for EAP re-sends
- CSCea01192: SPC crash on open
- CSCea03350: EAP identity request re-sends cause CSAuth to create new session
- CSCea03361: CSAuth processes EAP out-of-sync messages instead of ignoring
- CSCea03363: Torrent of EAP re-send messages can cause CSAuth to stuck
- CSCea03369: CSAuth send EAP-TLS messages with incorrect EAP ident field
- CSCea07381: Update VPN3K dictionary for v3.6
- CSCea19930: Leak in CSAuth when using IP based NARs
- CSCea35303: Change of NDG for NAS isnt applied until CSAuth is restarted manual
- CSCea55509: T+ max threads default should be changed to 200. (registry)
- CSCea55523: DEL/Buffer overflow in CSAdmin module can cause crash or hack
- CSCea67788: Change of NDG for NAS isnt applied until CSAuth is restarted manual
- CSCea75239: password expiry fails with acs 3.0.2 on memberserver
- CSCea75306: Need to reboot ACS server before modified user detail are recognised
- CSCea87621: Unknown user policy with ACE has returned inconsistent group inform
- CSCeb63025: duplicate selections from pull down menu of downloadable acl
- CSCeb63029: SPC names are limited to 31 characters in size
- CSCeb63034: restarting the services does not unlock locked object
- CSCeb64309: Network Model within ACS Registry grows in accounting
- CSCeb77357: ACS strips off CN from DN for GroupObjectType
- CSCeb84807: ACS strips off CN from DN for GroupObjectType
- CSCec00119: SQL accounting causes cslog crash for Ascend acct packet >=529&<=535
- CSCec00296: SQL accounting causes cslog crash for Ascend acct packet >=529&<=535
- CSCec06797: Unable to properly re-order LDAP group mappings
- CSCec12662: Unable to properly re-order LDAP group mappings
- CSCdw79587: Bad TACACS+ Authorization packets cause CSLOG to spin
- CSCdy15221: LDAP Group mapping disappears
- 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)
- CSCdz34158: resume install ends in err on not found files
- CSCdz44076: CSRadius preventing wlan APs failing over
- CSCdv63442: ODBC logging, Fractional truncation errors, not dropping connections
- CSCdv72785: Filter line is empty
- CSCdv75166: Radius accounting requests not validated fully as per RFC
- CSCdv89334: MSCHAP settings in NT/2000 Database configuration - not upgraded
- CSCdw04627: NULL response to AXENT challenge crashes CSAuth
- CSCdw07015: Class attribute missing from Radius Accounting section
- CSCdw11365: NULL password to Safeword crashes CSAuth
- CSCdw15116: ACS alters state attribute while passing it to easyRADIUS
- CSCdw15251: Certificate Setup Page - parsing certificate subject inadequate
- CSCdw22345: Replication fails on an upgraded ACS
- CSCdw27571: Global Authentication Configuration should be added as per adm privilege
- CSCdw29201: Distribution table and test accounts
- CSCdw31459: ODBC Authentication with CHAP/MSCHAP1/2 fails because of padding
- CSCdw34301: LDAP Group mapping reappears
- CSCdw40579: ACS 3.0 crash with Dr Watson Accounting request has no status type
- CSCdw42071: DB updates via RDBMS Sync do not cause replication
- CSCdw46931: ACS authenticates NDS expired/disabled users
- CSCdw50341: T+ enable partially broken for external db users
- CSCdw51174: Replication log message shows error on successful completion
- CSCdw52982: NAR doesnt match with wildcards in NAS definition
- CSCdw55453: NDS does not auth FQ usernames if they begin with . [dot]
- CSCdw55565: tacacs+ accounting is logged in tacacs+ administration logs
- CSCdw56666: EAP-TLS Certificate subject cn different than username
- CSCdw56671: EAP-TLS username in dotted format
- CSCdw63060: CSRadius fails to restart properly on Submit & Restart
- CSCdw66057: CryptoCard authentication fails - token-cacheing not functioning
- CSCdw78255: T+ crashes under load
- CSCdw79587: Bad TACACS+ Authorization packets cause CSLOG to spin
- CSCdw93069: Radius Proxy of accounting packets kill CSRadius
- CSCdx08524: Config tweaks to improve LEAP/EAP scalability
- CSCdx12381: Group names in ACS are disappearing intermittently
- CSCdx15267: Password change dynamically by the user doesnt cause DB replication
- CSCdx16853: Unable to clear account disable status with RDBMS synchronization
- CSCdx17622: sending crafted URL can cause CSADMIN to crash or exec user code
- CSCdx17689: unauthorized disclosure of data can be achieved using crafted URL
- CSCdx34079: voip accounting adds multiple user-name fields to reports
- CSCdx62520: When passwords are limited to alphanumeric, all CSMon tests fail
- CSCdx63893: LEAP problems due to AP out-of-sync packets
- CSCdx68751: External db lock prevents write to local log files
- CSCdx68848: CSUTIL add-nas do not flag replication of database
- CSCdx84564: Improve failed attempts message for invalid EAP request
- CSCdx85584: Large number of requests from unknown devices can slow server
- CSCdx85594: No Devices in Network Configuration after Replication
- CSCdx86614: CSMon should still monitor CSAuth during replication out
- CSCdx88709: Cross-Site Scripting to CSAdmin
- CSCdx88749: CSAdmin session is terminated while editing logging settings
- CSCdx88776: Shared Profile Components not upgraded
- CSCdx88809: Failed attempt of NDS cached user is logged incorrectly
- CSCdx90749: ODBC logging, Fractional truncation errors, not dropping connections
- CSCdx90751: NULL response to AXENT challenge crashes CSAuth
- CSCdx90752: NULL password to Safeword crashes CSAuth
- CSCdx90947: LDAP Group mapping reappears
- CSCdx93099: Automatic certificate enrollment is NOT functioning
- CSCdx94322: LEAP DLL rejecting users stopped AP failover
- CSCdx94441: Exception in CSRadius after DNIS/CLI check
- CSCdy01340: user CLID gets truncated after exporting into 3.0
- CSCdy02612: DCS assignment policy per NDG works incorrectly
- CSCdy03581: T+ Hang when Varsdb breaks
- CSCdy03810: IP-based NAR with denied locations works incorrectly
- CSCdy07198: ACS does not accept a user with subject cn different from the account
- CSCdy09527: Replication of all selected components upon Replicate Now cmd
- CSCdy10640: CSMon should test varsdb as workaround for CSCdx12381
- CSCdy13048: No default radio button selected
- CSCdy13056: CSMon Test login process causes to a dirty flag to be set on
- CSCdv61239: TACACS+ Command Accounting updates logged in user list
- CSCdv42366: Documentation wrong about admin failed attempts feature
- CSCdv41922: CSMon logs confusing message during replication
- CSCdv25235: Replication occurs every other time regardless on need
- CSCdv24984: / in port field of Network Access restriction breaks
- CSCdu87549: Timeouts required for LDAP searches
- CSCdu65240: Inter version replication failure error not logged
- CSCdu65230: Cross version replication error not in docs
- CSCdu65207: Windows DLL error logging inadequate
- CSCdu65095: add Usage Quota w/ Netscape in Interface Config removes options
- CSCdu63791: T+ enable partially broken for external db users
- CSCdu61901: Cant add userID in lowercase after adding it in uppercase
- CSCdu41846: Group map for LDAP fails with large numbers of groups
- CSCdu37391: RDBMS Sync docs are incomplete
- CSCdu36350: Documentation bug : LDAP and CHAP are not supported together
- CSCdu02875: CSNT documentation incorrect
- CSCdt91325: Delayed response to Safeword challenge crashes CSAuth
- CSCdt75695: When upgrading from 2.4 to 2.6 it doesnot update safeword token dll
- CSCdt73381: Set password source to External ODBC during RDBMS synchronization
- CSCdt72305: EAP-Message still available for edit in group profile
- CSCdt63400: CSNT port 2000 conflict with CCM
- CSCds43324: NDGs should be definable within NARs rather than individual NAS
- CSCdw22345: Replication fails on an upgraded ACS
|Note Caveats are printed word-for-word as they appear in our bug tracking system.|
Failed to Edit TACACS+ (Cisco IOS)
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.
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.
- In "IETF RADIUS Attributes" check the " 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
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.
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 Browser Versions section of the Release Notes for Cisco Secure Access Control Server for Windows 2000/NT Servers
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.
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.
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.
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.
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.
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.
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.
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.
Authentication services CSRadius and CSTacacs might crash when ACS 184.108.40.206 is installed on windows 2000 with service pack 1 and when safeword is used on a separate unix box. All users are safeword users.
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.
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.
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.
If you attempt to upgrade to Cisco Secure ACS 3.0.3 from 220.127.116.11 and abort installation of 3.0.3 before it is complete, using the clean.exe application that comes with 18.104.22.168 does not remove all related file system directories or registry keys.
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.
This behavior occurs after upgrading Cisco Secure ACS from 22.214.171.124 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.
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:
In the web GUI a black bar can sometimes appear in the page background when the page being displayed is very large (such as a list of several hundred NAS entries in Network Configuration). This is purely cosmetic and will not affect the server functionality, although it may make it difficult to read some information. The location of the bar may not be consistent on all servers as it's location depends completely on how the browser renders the page.
Workaround: Rename the page_background.gif file so that it does not get displayed. This will make the top line of the page unreadable (where it says "Select" or "Help") but will eliminate the black bars in the page. The page_background.gif file is located under
C:\Program Files\CiscoSecure ACS v3.x\CSAdmin\WWW\images by default.
After an ACS 3.0 server hangs (because of a hung/failed CSauth process) the WAPs trying to use this failed server should at some point timed out and failed over to another ACS server. This failover does not happen.
With AAA Accounting for exec sessions configured on a NAS, a user shows up in the Logged-In User report on ACS. With Accounting also configured for going into enable mode, the user no longer appears in the Logged-In User report after authenticating successfully.
Using MS-Text-Driver and accountaction.csv files to maintain user DB according: /en/US/products/sw/secursw/ps2086/products_user_guide_chapter09186a008007deac.html#2110
Re-running csdbsync (without changing accountaction.csv file) mostly solves this problem (correct imported, no error message on cli/logg-file). It also has happened during re-running, that csauth stopped and windows violation message box appeared.
In RFC 2246, the Server Hello has 4 bytes of gmt_unix_time and 28 bytes of random data. But, Server Hello from CiscoSecureACS has 4 bytes of garbage(00 00 00 00), 4 bytes of gmt_unix_time and 24 bytes of random data. Some clients may fail in authentication.
Conditions: The reason the Network Model is growing so large is that the packets do not have a traditional NAS-PORT value, and only in some cases do they contain the cisco VSA for nas-port (string version). Without a NAS-PORT the network model creates a port using the username.
Password change fails for RADIUS-based MS-CHAP v2 password change when the username submitted is not domain qualified. This happens regardless of whether ACS is installed on a domain controller or member server. RADIUS-based MS-CHAP v2 password change is supported only with Windows external user databases.
When Cisco Secure ACS is performing EAP-TLS authentications under a heavy load, some sessions that should end based on timeout values are ended with an Access Reject message instead. Under a lighter load, Cisco Secure ACS correctly responds with timeout messages instead of Access Reject.
Symptom: If the NAS is sending a username (IETF attribute 1) in a RADIUS access-request packet, which contains upper- and lower-case letters, the proxy ACS RADIUS will forward this access-request packet to the authenticating RADIUS server with all upper-case letters changed to lower-case letters
Conditions: - This is observed only when prefix stripping is configured on the proxy RADIUS ACS and the username contains the prefix to be stripped by the proxy RADIUS ACS. - This is not observed when suffix stripping or no stripping takes place.
When an external RADIUS database attempts to specify a user's group using Cisco IOS/PIX RADIUS attribute 1, [009\001] cisco-av-pair, and the group number specified is greater than 499, Cisco Secure ACS fails the user authentication and logs a seemingly unrelated error related to Group 100 and network access restrictions (even if no NARs are applied to the user).
After upgrading to 3.0.4, if you use a backup created by an older version of ACS, such as from 3.0.3, Cisco VPN 3000 RADIUS VSAs added in 3.0.4 disappear. The old backup file replaces the VSA configuration with a version that predates the addition of or changes to Cisco VPN 3000 VSAs 29, 61-68, and 75.
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated regularly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual or quarterly subscription.
For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour-a-day, award-winning technical support services, online and over the phone. Cisco.com features the Cisco TAC website as an online starting point for technical assistance. If you do not hold a valid Cisco service contract, please contact your reseller.
The Cisco TAC website (http://www.cisco.com/tac ) provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco TAC website is available 24 hours a day, 365 days a year.
Using the online TAC Case Open Tool (http://www.cisco.com/tac/caseopen ) is the fastest way to open P3 and P4 cases. (P3 and P4 cases are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using the recommended resources, your case will be assigned to a Cisco TAC engineer.
For P1 or P2 cases (P1 and P2 cases are those in which your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.
Priority 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Priority 3 (P3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
- Packet magazine is the Cisco quarterly publication that provides the latest networking trends, technology breakthroughs, and Cisco products and solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certification information, and links to numerous in-depth online resources. You can access Packet magazine at this URL:
This document is to be used in conjunction with the documents listed in the Related Documentation section.