|
|
Table Of Contents
Release Notes for Cisco Secure ACS for Windows Server Version 3.2.2
HTTPS Support Change and Management Center Applications
Changes to Token Server Support
Purchasing the Commercial Version
Upgrading to the Commercial Version
Supported Platforms for CiscoSecure Authentication Agent
Other Supported Devices and Software
Known Problems in Cisco Secure ACS Version 3.2.2
Resolved Problems in Cisco Secure ACS Version 3.2.2
Resolved Problems in Cisco Secure ACS Version 3.2.1
Obtaining Technical Assistance
Obtaining Additional Publications and Information
Release Notes for Cisco Secure ACS for Windows Server Version 3.2.2
June 2005
These release notes pertain to Cisco Secure Access Control Server for Windows Server (Cisco Secure ACS) version 3.2.2.
These release notes provide:
•
HTTPS Support Change and Management Center Applications
•
•
–
–
•
•
New Features
Cisco Secure ACS version 3.2 contains the following new features:
•
•
•
•
•
–
–
–
–
–
Cisco Secure ACS 3.2 allows flexible EAP settings—one or several EAP types can be selected concurrently—enabling Cisco Secure ACS to intelligently process EAP authentications depending on the 802.1X supplicant.
•
•
Tip
Supplemental License Agreement for Cisco Systems Network Management: Cisco Secure Access Control Server Software
IMPORTANT—READ CAREFULLY: This Supplemental License Agreement ("SLA") contains additional limitations on the license to the Software provided to Customer under the Software License Agreement between Customer and Cisco. Capitalized terms used in this SLA and not otherwise defined herein shall have the meanings assigned to them in the Software License Agreement. To the extent that there is a conflict among any of these terms and conditions applicable to the Software, the terms and conditions in this SLA shall take precedence.
By installing, downloading, accessing or otherwise using the Software, Customer agrees to be bound by the terms of this SLA. If Customer does not agree to the terms of this SLA, Customer may not install, download or otherwise use the Software.
1.
•
–
•
2.
Please refer to the Cisco Systems, Inc. Software License Agreement.
Product Documentation
Note
Table 1 describes the product documentation that is available.
Table 1 Product Documentation
Release Notes for Cisco Secure ACS for Windows Server
•
•
•
a.
b.
Installation Guide for Cisco Secure ACS for Windows Server
•
•
a.
b.
•
User Guide for Cisco Secure ACS for Windows Server
•
•
a.
b.
•
Installation and User Guide for Cisco Secure ACS User-Changeable Passwords
•
•
a.
b.
Supported and Interoperable Devices and Software Tables for Cisco Secure ACS for Windows Server
1.
2.
Recommended Resources for the Cisco Secure ACS User
1.
2.
Online Documentation
In the Cisco Secure ACS HTML interface, click Online Documentation.
Online Help
In the Cisco Secure ACS HTML interface, online help appears in the right-hand frame when you are configuring a feature.
1 See the "Obtaining Documentation" section.
Related Documentation
Note
Table 2 describes a set of white papers about Cisco Secure ACS. All white papers are available on Cisco.com. To view them:
1.
2.
Installation Notes
For information about installing Cisco Secure ACS, see Installation Guide for Cisco Secure ACS for Windows Server, version 3.2.
HTTPS Support Change and Management Center Applications
Cisco Secure ACS version 3.1 introduced support for HTTPS to protect administrative access to the HTML interface. In response to a problem discovered in Cisco Secure ACS 3.1 (see bug ID CSCea40150 in Table 5), Cisco Secure ACS does not allow HTTP and HTTPS to function simultaneously.
Multi-device management applications, such as Management Center for Firewalls, can be configured to use Cisco Secure ACS for authentication of administrators and authorization of their actions. Communication between early versions of multi-device management applications and Cisco Secure ACS requires HTTP. If you enable HTTPS in Cisco Secure ACS 3.2, communication between multi-device management applications and Cisco Secure ACS fails.
If you use Cisco Secure ACS with a multi-device management application that is not yet capable of HTTPS for communicating with Cisco Secure ACS, you must disable HTTPS in Cisco Secure ACS; otherwise, integration with Cisco Secure ACS fails.
Note
Changes to Token Server Support
Token server support in Cisco Secure ACS 3.2 is identical to that in Cisco Secure ACS 3.1; however, if you upgrade from Cisco Secure ACS 2.6.4 or Cisco Secure ACS 3.0.2 and you use token server databases, you should understand the changes to token server support that we began with Cisco Secure ACS 3.0 and completed in Cisco Secure ACS 3.1.
Beginning with Cisco Secure ACS 3.0.1, we supported CRYPTOCard token servers using a standard RADIUS interface. Cisco Secure ACS 3.1.1 extended the use of RADIUS to all token servers except RSA SecurID. For RSA SecurID, the vendor-proprietary interface is used.
If you upgrade to Cisco Secure ACS 3.2, the installation program may prompt you for information about token servers, depending on the version of Cisco Secure ACS you are upgrading from and the token server databases detected by the upgrade process.
•
–
–
•
–
–
–
With this information, the installation program replaces the older token server configuration with a new one that uses the RADIUS interface of the token server. For more information about RADIUS support by your token server, see the applicable token server documentation.
Note
Evaluation Version
The evaluation version of Cisco Secure ACS 3.2 provides full functionality for 90 days after the date of installation. This allows you to use all features of Cisco Secure ACS 3.2 while determining if it suits your needs. The evaluation version of Cisco Secure ACS 3.2 will be available within 30 days after the release of the commercial version of Cisco Secure ACS 3.2.
The evaluation version of Cisco Secure ACS 3.2 can be distinguished from the commercial version in the following ways:
•
•
•
When the evaluation period has elapsed, the CSRadius and CSTacacs services fail to start. You will receive a message upon accessing the Cisco Secure ACS HTML 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.2 online, use the following URL:
http://www.cisco.com/pcgi-bin/cm/welcome.pl
Upgrading to the Commercial Version
Note
After purchasing a commercial version of Cisco Secure ACS 3.2, 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.2, follow the instructions in Installation Guide for Cisco Secure ACS for Windows Server, version 3.2.
Limitations and Restrictions
The following limitations and restrictions apply to Cisco Secure ACS 3.2.1.
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.
Supported Upgrade Versions
We tested upgrading to Cisco Secure ACS 3.2.1 from the following previous versions:
•
•
•
Supported Operating System
Cisco Secure ACS for Windows Servers 3.2.2 only supports two versions of the Windows 2000 operating system, as listed below. Both the operating system and the service pack must be English-language versions.
•
•
–
–
–
Note
•
•
Windows 2003 Server is not a supported operating system; however, we do support authenticating users with Windows 2003 Active Directory. For more information, see Windows Server 2003 Support.
Tested Windows Security Patches
We tested Cisco Secure ACS for Windows Servers version 3.2.2 with the following Microsoft security patches installed:
•
•
•
•
•
•
•
Windows Server 2003 Support
Cisco Secure ACS supports authentication using Active Directory on Windows 2003 Server as an external user database, including support for password aging and machine authentication.
Note
Upgrading from Windows NT 4.0
If you are upgrading from a previous version of Cisco Secure ACS that is running on Windows NT 4.0, you cannot upgrade the operating system to Windows 2000 Server. This is because the setup program for previous versions of Cisco Secure ACS detected which Windows operating system the computer used and customized Cisco Secure ACS for that operating system. As a result, upgrading the operating system to Windows 2000 Server without taking the necessary steps causes Cisco Secure ACS to fail.
We last published information about how to upgrade the operating system of the computer running Cisco Secure ACS to Windows 2000 in the documentation for Cisco Secure ACS 3.1. For more information, log in to Cisco.com and select Products & Services > Security and VPN Software > Cisco Secure Access Control Server for Windows > Technical Documentation > Installation Guides > Installation Guide for Cisco Secure ACS for Windows Server > Installation Guide for Cisco Secure ACS for Windows Server 3.1.
Supported Web Browsers
To administer all features included in Cisco Secure ACS 3.2, use an English-language version of one of the following tested and supported web browsers:
•
•
•
We do not support other versions of these browsers, nor do we test web browsers by other manufacturers.
Note
•
•
•
•
Supported Platforms for CiscoSecure Authentication Agent
For use of CiscoSecure Authentication Agent with Cisco Secure ACS 3.2.1, we support CiscoSecure Authentication Agent on the following client platform operating systems:
•
•
On the following client platform operating systems, we do not support the use of CiscoSecure Authentication Agent with Cisco Secure ACS 3.2.1:
•
•
•
Other Supported Devices and Software
For information about supported Cisco devices, external user databases, and other software, see Supported and Interoperable Devices and Software Tables for Cisco Secure ACS for Windows Server Version 3.2. To see this document, log into Cisco.com and select Products & Services > Security and VPN Software > Cisco Secure Access Control Server for Windows > Technical Documentation > Device Support Tables.
Known and Resolved Problems
This section contains information about the following topics:
•
•
•
Cisco AAA Client Problems
Refer to the appropriate release notes for information about Cisco AAA client problems that might affect the operation of Cisco Secure ACS. You can access these release notes online at the following URLs.
Cisco Aironet Access Point
http://www.cisco.com/univercd/cc/td/doc/product/wireless/
Cisco BBSM
http://www.cisco.com/univercd/cc/td/doc/product/aggr/bbsm/
Cisco Catalyst Switches
http://www.cisco.com/univercd/cc/td/doc/product/lan/
Cisco IOS
http://www.cisco.com/univercd/cc/td/doc/product/software/
Cisco Secure PIX Firewall
http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/
Cisco VPN 3000 Concentrator
http://www.cisco.com/univercd/cc/td/doc/product/vpn/vpn3000/
http://www.cisco.com/univercd/cc/td/doc/product/vpn/vpn3002/
Cisco VPN 5000 Concentrator
http://www.cisco.com/univercd/cc/td/doc/product/aggr/vpn5000/
Known Problems in Cisco Secure ACS Version 3.2.2
Table 3 describes problems known to exist in this release.
Note
Note
Table 3 Known Problems in Cisco Secure ACS for Windows Server, Version 3.2.2
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 HTML in the browser interface.
Workaround/Solution: Use a context list no longer than 4096 characters.
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.
CSCdx19854
Memory check for certificates in https transport is required
When you select the "Use HTTPS Transport for Administration Access" check box on the Access Policy page and more than two HTTPS sessions are active, the following error is presented:
Can't initialize HTTPS transport: too many active HTTPS sessionsSSL Admin design does not enforce a restriction that prevents the modification of Cisco Secure ACS certificates so that there are not more than two certificates in memory at once.
Instead Cisco Secure ACS prevents the initialization of HTTPS when more than two HTTPS sessions are in use.
Workaround/Solution: Reduce the number of concurrent administrative sessions to two or one before attempting to enable HTTPS using the new certificate.
CSCdy51214
fail to delete aaa server when its in sync table/aaa server side
A AAA server cannot be deleted from the "(Not Assigned) AAA Servers" table in Network Configuration if the Synchronize"= list under Synchronization Partners on the RDBMS Synchronization Setup page is empty. An error message "x.x.x.x can not be deleted since it is an synchronization partner" appears.
Workaround/Solution: Move any other AAA server to the Synchronize list, then delete the AAA server.
CSCdy59706
CAA messaging wont work with ppp callback and callin authentication
When having ppp callback and only callin is authenticated (ppp authentication pap chap callin), then messaging to the CAA client will fail with all aging rules selected in ACS.
This is a documentation bug, the above won't work without changes.
Workaround/Solution: Either remove the "callin" keyword to enable authentication for callin and callout (callback in this scenario), or disable callback altogether.
CSCdz13771
err in csauth in every X min replication-certain flow
if nases or users are added during replication, replication may fail on next replication cycle.
workaround: added a new nas or user.
Replication fails in very particular circumstances:
•
•
•
•
•
Workaround/Solution: Restart the CSAuth service.
CSCdz61464
Solaris Netscape 7.0 - Minor Features Failure
When the administrative browser is Netscape 7.0 on Solaris 8.0, some menus in the HTML interface for Cisco Secure ACS do not work properly.
Workaround/Solution: Use a supported Windows browser.
CSCdz61529
Netscape hangs on several times during login session on Solaris
When you use Netscape 7.0 to access the HTML interface of Cisco Secure ACS, the browser stops responding after you access the User Setup page or while trying to add a shared profile component.
Workaround/Solution: Use a supported Windows browser.
CSCdz61875
Configured Default Proxy Distribution Entry is not restored
If you configure the (Default) of "Proxy Distribution Table" in "Network Configuration" after backed up. Previously settings before backup are not restored. Example...
•
•
•
•
•
Workaround: There is no workaround.
CSCdz86955
Cannot remove shell authorization from groups display
Shell command authorization remains in the User Setup and Group Setup sections of the HTML interface, even after shell command authorization is disabled in Interface Configuration and the feature is not in use.
Workaround/Solution: None at this time.
CSCea25090
Logged In User not showing after going into enable mode on router
With AAA Accounting for exec sessions configured on a NAS, a user shows up in the Logged-In User report on Cisco Secure ACS. With Accounting also configured for going into enable mode, the user no longer appears in the Logged-In User report after authenticating successfully.
Cisco Secure ACS tracks user sessions by IP address and port number. When enable authentication succeeds, Cisco Secure ACS sees that the IP address and port number combination for the existing session have been reused and assumes that the accounting stop packet was not sent or was lost; therefore, the user session is removed from the Logged-In User report even though the session continues in enable mode.
Because the NAS cannot be configured to send new accounting start packets when the enable mode is entered, the Logged-In User report cannot correctly report the user session as ongoing.
Workaround: None.
CSCea39639
RDBMS sync randomly fails with ERROR Reason -No Error
Symptom: Using MS-Text-Driver and accountaction.csv files to maintain user DB according:
http://www.cisco.com/univercd/cc/td/doc/product/
access/acs_soft/csacs4nt/csnt30/user/s.htm#2110randomly skips or truncated data.
Syntax of accountaction file is correct. Sometimes error message is logged like:
CSDbSync 03/07/2003 12:39:49 E 0000 2688 Error: host '<hosname>' Action failed (SI=44 A=176 UN='cisco123' GN='' AI='' VN='tcp/23' V1='permit' V2='10.1.1.1' V3='') Reason - No ErrorRe-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.
CSCea55457
Radius Attributes do not appear in user/group profile page
After you enable RADIUS attributes in the Interface Configuration section of the Cisco Secure ACS HTML interface, they do not appear or appear only partially in Group Setup or User Setup, as applicable.
Workaround/Solution: Restart the CSAdmin service.
CSCea60497
no msg in rdbms log on the sync partner about the sync operation
When a Cisco Secure ACS Appliance receives RDBMS Synchronization data from a primary ACS, the RDBMS Synchronization log on the secondary ACS does not record the synchronization event, regardless of success or failure.
Workaround/Solution: None at this time. You may be able to deduce when synchronization occurred and whether it succeeded by reading the synchronization logs and reviewing the RDBMS Synchronization configuration on the primary ACS.
CSCea67901
UCP has trouble with dots in usernames
When using the User changeable passwords utility to change the passwords for the usernames which contain dot (".") character, after clicking on one of the links on the top, the links at the top in the subsequent screen contain only the part of the username before the dot.
Workaround: edit the passwd.htm and result.htm files in the cgi-bin directory to comment out the table with the links - so that the users would not be able to get confused.
CSCea71759
Headline of UCP application stating Cisco Secure ACS
The web pages of the User-Changeable Passwords (UCP) utility have titles and headings that suggest that the user is logging into Cisco Secure ACS for an administrative session. This is not possible from UCP and the headings and titles are erroneous.
Workaround/Solution: Educate users about the function of UCP or modify the HTML file contents to change the misleading titles and headings.
CSCea74289
cascade replication due to user pass change-dont work
Cascading replication does not occur when the replication trigger is user password change and the primary Cisco Secure ACS is configured to perform replication manually.
Workaround/Solution: Use scheduled replication on the primary Cisco Secure ACS.
CSCeb11691
SPC names are limited to 31 characters in size
SPC names are limited to 31 characters in size not 32 as the doc below specifies.
http://www.cisco.com/en/US/products/sw/secursw/
ps2086/products_user_guide_chapter09186a00800
d9e6b.htmlCSCeb15219
Couldnt add NAS filter by CSDdsync
When you attempt to add a network access restriction using RDBMS Synchronization, action code 122 "ADD_NAS_ACCESS_FILTER" doesn't work. When you use the UN variable, the error message "The named user variable cannot be found" is logged even though the user exists in the CiscoSecure user database.
Workaround/Solution: Synchronization with action code 122 succeeds after you manually select the "Define IP based access restrictions" option in user profile.
CSCeb16968
ACS shared profile components disappear after ACS upgrade
After you upgrade Cisco Secure ACS, authorization support for Management Center (MC) applications, such as Management Center for Firewalls, fails. In the Shared Profile Components section of the Cisco Secure ACS HTML interface, each MC that has registered with Cisco Secure ACS has a set of pages for configuring authorization components. If you access a page for editing or adding authorization components, you see an error message about a missing XML file.
Workaround/Solution: You must use CiscoWorks to re-register all MCs with Cisco Secure ACS.
Log into the CiscoWorks desktop with admin privileges.
Go to Server Configuration > Setup > Security > Select Login Module. Configure CiscoWorks to use the CiscoWorks Local module, and then configure CiscoWorks to use the TACACS+ module.
Go to VPN Security Management Solution > Administration > Common Services > Configuration > AAA Servers. Unregister all MCs and then re-register all MCs.
Log out of CiscoWorks.
CSCeb23766
Inconsistency with ACS response if username contains invalid chars
Radius usernames entered with invalid characters results in the ACS server not sending any response at all. This can cause the NAS to fail over to the configured secondary authentication method which may not be desirable.
Workaround: At the present time, TACACS authentication does not appear to have this same problem.
CSCeb32885
schedule backup don't work properly
In the evaluation version of ACS 3.2 scheduled backups might not always operate. This has been observed when Cisco Secure ACS contained 60000 users and 1200 AAA Clients.
After a while scheduled backup resumed its proper operation and returned to normal. The reason is not clear, and requires further investigation.
Workaround: None.
CSCeb34179
CSRadius fail to stop when 90 days evaluation period is over
After the 90-day evaluation period had passed, the evaluation version of Cisco Secure ACS for Windows Server develops problems with the CSRadius service if a RADIUS request is received. The CSRadius service begins to stop but never successfully complete the stop process. The service status appears as "stopping". After this point, folders under the Cisco Secure ACS installation directory are locked and an upgrade to the commercial version cannot be completed. Neither can the trial version be successfully uninstalled.
Workaround/Solution: Reboot the server and uninstall or upgrade Cisco Secure ACS before a RADIUS request is received. To ensure that no RADIUS requests are received, consider taking the server off of the network long enough for the installation to succeed. As an alternative, you could change the IP address of the server to an address that RADIUS clients are not configured to send requests to.
CSCeb36966
large number Windows groups causes ACS GUI timeout
When there is a large number of Windows groups (this was observed with 25000), the ACS http GUI connection times out.
Workaround/Solution: Force the Windows server that Cisco Secure ACS uses to retrieve the groups to cache the groups locally. Go into Active Directory Users and Groups on the computer running Cisco Secure ACS for Windows Server. If you are using Cisco Secure ACS Solution Engine, go into Active Directory Users and Groups on the computer running the Cisco Secure Remote Agent for Windows, In Active Directory, view all the groups. In Cisco Secure ACS, configure the mappings. This works because the server has cached the information.
CSCeb43948
Could not generate valid Password with password length => 9
If, in System Configuration > Local Password Management, you configure Cisco Secure ACS to require user passwords to be nine or more characters in length, Cisco Secure ACS generates "Could not generate valid Password" messages in the logs for the CSMon service. The message appears on the schedule you define for CSMon to test services. This has been verified as a problem on 3.1 and 3.2. Earlier versions were not tested, but likely have the problem.
Workaround: None.
CSCeb45624
NAR does not work comma separated source address
The documentation and the short help pages in the browser indicate that you can specify multiple IP addresses separated by commas for a source IP in the IP-based NAR section. This is not true. Any attempt to actually do so will result in Cisco Secure ACS ignoring the NAR config for the telnet connections to a router. This has been verified in ACS 3.2 and ACS 3.1.
Workaround: Do not use commas to separate multiple IP addresses in NARs.
CSCeb51393
multi-admin needs to be able to add/edit/delete downloadable ACLs
In the evaluation version of ACS 3.2 scheduled backups might not always operate. This has been observed when Cisco Secure ACS contained 60000 users and 1200 AAA Clients.
After a while scheduled backup resumed its proper operation and returned to normal. The reason is not clear, and requires further investigation.
Workaround: None.
CSCeb58021
Server Hello packet of TLS from ACS Server has garbage.
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.
There is no workaround.
CSCeb58107
cisco-nas-port attribute should be included in VoIP accounting log
The cisco-nas-port attribute should be available in the VoIP accounting log.
CSCeb62898
Group mapping ordering applet is not properly ordered
In a newly created Windows group mapping configuration, group mappings list in the wrong order.
Workaround: On the page for ordering group mappings, order the group mappings and click Submit. As additional mappings are added, they appear properly at the end of the list of mappings.
CSCeb63188
database define with special chars permitted but unusable later
Symptom: ACS allows definition of a database with special characters in the name, like "Windows (test)" but on trying to actually use the database in the 'Selected Databases' column with 3.0.3 & 3.2, the error message is 'The selected DB search list is empty'. The software should not allow naming of a database when the name cannot be used.
Workaround: Do not use special characters in a database name.
CSCeb82136
ACL size 35K cannot be edited - The page cannot be displayed
If you create a downloadable ACL that is larger than 32KB (roughly 32,000 characters, including name and description), when you try to edit it later, the browser shows a "page cannot be displayed" error.
Workaround: Do not add or edit a downloadable ACL so that it is larger than 32KB.
CSCec00789
Calling-Station-ID attribute description inaccurate
In the user guide for Cisco Secure ACS, RADIUS IETF attribute 31, Called-Station-ID is inaccurately documented as only being supported for ISDN and modem calls for AS5200s. This is not true.
Cisco Secure ACS supports this attribute regardless of what type of AAA client sends it.
CSCec05303
VPN3000 downloadable ACL not working on upgraded ACS
If a previous version of ACS is upgraded to ACS 3.2, the Downloadable ACL feature will not work with a VPN3000 concentrator. It works fine on a new install. If the following registry key is added, it works. No values are required within the key:
REGEDIT4 [HKEY_LOCAL_MACHINE\SOFTWARE\Cisco\CiscoAAAv3.2\CSRadius\ExtensionPoints\003\AssociateWithVendors\005]
CSCec06340
acs is miscalculating the user-password when proxying
Symptom: in such a topology:
nas---> acs1 proxy ----> radius band when using the proxy distribution table to do the proxy.
When acs 3.1 and later is being used as a proxy server, when it re-calculates the user-password attribute in order to forward it to the end radius server, it miscalculates the user-password attribute. if the same pre-shared key is being used between acs1 and radius b, then in principal the same user-password should be calculated, but it's not and usually that user-password attribute gets same values as first couple of bytes of the original user-password while the rest are zeros.
This problem has been observed in acs 3.1 and 3.2 released versions. It also might be in 3.0.
This problem doesn't happen when proxying between 2 acs servers. it only happens between an acs server and some 3rd party server due to the way the password is calculated.
Workaround: instead of using proxy distribution table to do the proxy in acs 1, configure radius b as a "radius token server" in external databases, and configure unknown user policy on acs1 to check radius b. of course in that case on radius b you should configure acs 1 as a network device and give it the correct pre-shared secret configured in radius token server on acs1.
CSCec18522
PIX downloadable ACLs do not allow -; no pix object groups
The Cisco Secure ACS downloadable ACL feature does not allow hyphens, "-", in ACL definitions; however, the PIX Firewall access-list command has a "object-group" keyword. You cannot configure downloadable ACLs in Cisco Secure ACS using the object-group keyword.
Workaround: None at this time.
CSCec18573
Replication of VMS configurations requires restart of CSAdmin
VMS-specific attributes replicated to secondary Cisco Secure ACS are not available. This also prevents a CiscoWorks administrator from registering an application with the secondary Cisco Secure ACS.
Workaround: Restart the CSAdmin service. After this service is restarted, registration from CiscoWorks succeeds and the VMS configuration data replicated to the secondary Cisco Secure ACS is available in the HTML interface.
CSCec39523
Proxy ACS changes upper case letters to lower in username RADIUS att
Topology:
NAS--proxy RADIUS ACS--authenticating RADIUS server
Symptom: If the NAS is sending a username (IETF attribute 1) in a RADIUS acces-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.
Workaround: Do not use upper-case letters in the username attribute, when performing prefix stripping
CSCec46370
Group mapping misbehavior
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 "500", 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). Specifying a group number larger than 500, such as 501, functions as expected, with the user assigned to the Default group.
RADIUS group specification requires that the assignment in the cisco-av-pairattribute use the following format:
ACS:CiscoSecure-Group-Id = Nwhere N is the Cisco Secure ACS group number (0 through 499) to which Cisco Secure ACS should assign the user.
Workaround: Ensure that the external RADIUS server database only specifies a group number between 0 and 499.
CSCec61110
authentications on secondary acs may fail after replication
Symptom: In environment where primary and secondary Cisco Secure ACS primary and secondary servers are kept in synch using the replication feature, user authentication may fail for users defined in an external database users and the Failed Attempts log will contain an "external DB not configured" error.
Conditions: This happens with certain external database types such as LDAP, NDS, and the various token server types. It can't happen with the Windows external DB. By configuring external databases in a different order on the primary and secondary Cisco Secure ACS servers, authentication fails on the secondary server for users defined in the databases configured in a different order. If external databases are configured in same order on primary and secondary servers, this does not happen. For example, if you configure two instances of LDAP external user databases on primary and secondary servers but configure them in different orders, after users are replicated, LDAP authentication attempts fail on the secondary server.
Workaround: For each database type involved in the problem, delete the external databases on all secondary servers and reconfigure them in the same order that they are defined on the primary server. If this fails, delete the affected external databases on the primary and secondary servers and reconfigure them.
CSCec63624
ACS 3.2 admin gui locks and displays action canceled message
If the Shell (exec) service is disabled in Interface Configuration > TACACS+ (Cisco IOS) and you attempt to access a group other than the default group, the Cisco Secure ACS HTML interface ends the administrative session.
Workaround: To start a new session, close the browser window, open a new browser window, and access the HTML interface again.
To permit access to groups other than the default group, enable the group-level Shell (exec) service in Interface Configuration > TACACS+ (Cisco IOS).
CSCec71687
need to change the source from which ACS reads certificate from stor
When you attempt to install a certificate from storage, Cisco Secure ACS expects to find the certificate in the Trusted Root Certification Authorities folder of the Local Computer Account certificates. If you have previously installed a certificate using the Cisco Secure ACS HTML interface, you cannot reinstall the certificate from storage.
Workaround: To reinstall from storage a certificate previously installed using the Cisco Secure ACS HTML interface, use the Microsoft Management Console to access the certificates for the local computer account and move the stored certificate from the ACS certificates folder you find it in to the Certificates folder under Trusted Root Certificate Authorities.
CSCec73065
csutil sometimes messes up SPC NARs
Symptom: In Cisco Secure ACS for Windows Server 3.2, if you re-initialize the internal database by doing "csutil -q -d -n -l" or if you dump your databases using "csutild -d" and rampart by doing "csutil -l", Network Access Restrictions defined in the Shared profile Component section of the HTML interface may lose all of the permitted/denied calling point entries.
Workaround: The problem is in the Description Edit box of Network Access Restriction page. This box must NOT contain any <Enter> symbols (<CR><LF> or hard-breaks), including at the end of the line.
Delete all hard-breaks from Description by pressing <Backspace>. Let the web browser automatically wrap lines. Do not attempt to force line breaks with returns.
CSCec74461
RSA Next Tokencode mode not work via Cisco PEAP due to timeout
"Next passcode" mode for RSA token card users may not succeed with a Cisco PEAP client if the timeout value on the AAA client is not sufficient. This is primarily an issue with Cisco Aironet, as Access Points do not have configurable timeouts.
Workaround: The issue lies in the AAA client, not Cisco Secure ACS. If the timeout value is configurable, you can increase it; however, if it is not sufficient, users must attempt to start a new session in order to use a new passcode.
CSCed01627
Protocol Error in Login
When you log into the HTML interface of Cisco Secure ACS, you may receive a protocol error and be unable to access the HTML interface. This applies to both Cisco Secure ACS for Windows Servers and Cisco Secure ACS Solution Engine.
Workaround: Restart CSAdmin service.
CSCed01640
Memory leak in CSAuth caused with Leap-Proxy scenario
When you use LEAP proxy with Cisco Secure ACS under stress, the CSAuth service uses additional system memory and does not release the memory when the stress is removed from the system.
Workaround: Restart the CSAuth service.
CSCed10382
PAP authentications to LDAP causes mem leak in CSAuth & CSRadius
When running PAP authentications for several hours (1.4 million authentications) against an LDAP external user database, CSAuth usage is 283 MB. This indicates that CSAuth has a memory leak.
Workaround: If CSAuth memory usage becomes a problem, restart CSAuth.
CSCed15862
CSAuth crashes upon PEAP stress because SSL-C library
Under a sustained heavy PEAP authentication load, the CSAuth service may crash. In testing, this occurred after 60,000 successful authentications.
Workaround: Restart the CSAuth service.
CSCed18334
CSDBSync logs become swollen with time
CSDBSync logs grow very large and contain many "WaitForMultipleObjects returned [-1]" messages. CPU usage may also be very high. The issue is likely caused by starting services in the wrong order. If this occur with Cisco Secure ACS for Windows Server rather than Cisco Secure ACS Solution Engine, the services that make up Cisco Secure ACS may be running as different user accounts rather than as the same user account for all Cisco Secure ACS services.
Workaround: If you are using Cisco Secure ACS for Windows Server, verify that all Cisco Secure ACS services are running as the same user account. To do so, go to Start > Settings > Control Panel > Administrative Tools > Services and view the properties of each Cisco Secure ACS service.
Reboot the Cisco Secure ACS server. When the server reboots, services automatically start in the correct order and the problem should abate.
CSCin45582
VMS2.2-BT:Shared Profile components are not overwritten
If you re-register a Management Center application with Cisco Secure ACS, Cisco Secure ACS retains the authorization settings from the previous registration rather than replacing them with default authorization settings.
Workaround/Solution: None.
Resolved Problems in Cisco Secure ACS Version 3.2.2
Table 4 describes problems resolved since the last release of Cisco Secure ACS for Windows Server.
Note
Resolved Problems in Cisco Secure ACS Version 3.2.1
Table 5 describes problems resolved since the last release of Cisco Secure ACS for Windows Server.
Note
Obtaining Documentation
Cisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation on the World Wide Web at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
International Cisco websites can be accessed from this URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
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.
Registered Cisco.com users can order a single Documentation CD-ROM (product number DOC-CONDOCCD=) through the Cisco Ordering tool:
http://www.cisco.com/en/US/partner/ordering/ordering_place_order_ordering_tool_launch.html
All users can order annual or quarterly subscriptions through the online Subscription Store:
http://www.cisco.com/go/subscription
Click Subscriptions & Promotional Materials in the left navigation bar.
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•
http://www.cisco.com/en/US/partner/ordering/index.shtml
•
Documentation Feedback
You can submit e-mail comments about technical documentation to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
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.
Cisco TAC Website
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.
Accessing all the tools on the Cisco TAC website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:
http://tools.cisco.com/RPF/register/register.do
Opening a TAC Case
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.
To open a case by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447For a complete listing of Cisco TAC contacts, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
TAC Case Priority Definitions
To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.
Priority 1 (P1)—Your network is "down" or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
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.
Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/en/US/products/products_catalog_links_launch.html
•
•
•
http://www.cisco.com/go/iqmagazine
•
http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html
•
http://www.cisco.com/en/US/learning/index.html
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Copyright © 2003 Cisco Systems, Inc. All rights reserved.
Posted: Fri Jul 8 14:51:16 PDT 2005
All contents are Copyright © 1992--2005 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
