FIX: A password change on an external system may fail when you use Enterprise Single Sign-On (SSO) in Host Integration Server 2004 to perform password synchronization

When you use Enterprise Single Sign-On (SSO) in Microsoft Host Integration Server 2004 to perform password synchronization, a password change on an external system may fail. An example of an external system is an IBM mainframe.

The password change on the external system may fail when the following conditions are true:

�

The affiliate application that was created for the external system was defined by using more than two application fields. The first application field defines the user ID for the external system. Typically, the second application field defines the password for the external system. Some external systems may require additional credential types that can be defined as additional application fields in the affiliate application. An example of an additional credential type is an employee ID.

�

The Password Synchronization Adapter that is used for the external system is configured to send the external system's previous password as part of the password change request. The Password Synchronization Adapter sends the previous password if the sendOldPassword parameter is set to yes in the XML file that is used to create the Password Synchronization Adapter.

Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

File name	File version	File size	Date	Time	Platform	SP requirement
Infocache.dll	4.0.123.0	70,144	28-Jun-2005	21:24	x86	SP1
Ssolookupserver.dll	4.0.123.0	80,896	28-Jun-2005	21:24	x86	SP1
Ssomappingserver.dll	4.0.123.0	60,928	28-Jun-2005	21:24	x86	SP1
Ssopsserver.dll	4.0.123.0	114,688	28-Jun-2005	21:25	x86	SP1
Ssox4.sql	Not applicable	28,188	16-Jun-2005	22:53	Not applicable	SP1

Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about Enterprise SSO and password synchronization, see the following white paper that is named "Single Sign-on Services for Microsoft Enterprise Application Integration Solutions": For more information, click the following article number to view the article in the Microsoft Knowledge Base: The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.