This bulletin describes the contents of the Cisco® Secure Services Client Release 4.2. The new release contains feature enhancements and bug fixes identified from the previous product release. Release 4.2 is scheduled to be generally available on August 2, 2007.
New or Changed Features
Customizable Login and Password Strings
The Cisco Secure Services Client Release 4.2 allows the administrator to configure specific strings to be displayed in place of the username and password. This simplifies the user experience in organizations that have unique names for usernames and passwords.
Outer Identity Pattern Assignment
In a deployed network configuration, the administrator can specify the content of the initial Extensible Authentication Protocol (EAP) response/identity message. For tunneled EAP methods, this content represents the phase 1, outer (unprotected) tunnel. Additionally, the administrator can specify the content of the EAP identity response of any phase 2, inner tunnel (protected identity). In both cases, the configuration consists of fixed text that you explicitly define and placeholder keywords that represent variable values for certain standard components of a network access identifier (NAI) that are dynamically supplied by Cisco Secure Services Client at the time of authentication processing. This flexibility always you to use any standard or special formats compatible with your credential storage environment and the requirements of your authentication server.
Bug or Problem
Failure to start Cisco Secure Services Client.
A fix is implemented for an unusual Windows login sequence on a small percentage of machines
Multiple deployment packages.
If more than one distribution package XML is located in the deployment folder, Cisco Secure Services Client now finds and processes the most recent valid file and then removes all other files. In the previous releases, only a single distribution package file was allowed in the folder.