The Enterprise Single Sign-On service that is included with Host Integration Server 2004 does not support case-sensitive SSO databases (887962)

SUMMARY

The Enterprise Single Sign-On (ENTSSO) service that is included with Microsoft Host Integration Server 2004 does not support case-sensitive SSO databases.

If you use the ENTSSO service together with a case-sensitive SSO database, errors may occur in the ENTSSO system.

The current behavior of the ENTSSO service is case preserving, not case sensitive.

For example, you create an affiliate application that is named AffApp1. Because the case is preserved, the application name is stored in the SSO database as AffApp1. The ENTSSO administration utilities can refer to the affiliate application as AFFAPP1, as affapp1, or as any other combination of uppercase and lowercase characters because the ENTSSO service is case insensitive.

If an instance of Microsoft SQL Server that hosts the SSO database is configured to use binary collation, the databases that are created on that instance of SQL Server will be case sensitive. In a case-sensitive database, an affiliate application that is named AffApp1 cannot be referred to as AFFAPP1 or affapp1 because the two names are now distinct.

MORE INFORMATION

The ENTSSO service has been updated to correctly detect and support case-sensitive SSO databases. After you apply the following software update, the ENTSSO service detects whether the SSO database is case sensitive. If the SSO database is case sensitive, the ENTSSO service operates in case-sensitive mode. If the SSO database is not case sensitive, the ENTSSO service operates in its regular case-insensitive and case-preserving mode.

Notes

Microsoft Windows accounts that are stored in the SSO database are never case-sensitive and are always converted to uppercase before they are written to the SSO database. For example, the Windows user account domain1\user1 is stored in the SSO database as DOMAIN1\USER1.
To obtain the correct case-sensitive behavior on instances of SQL Server that are configured to use binary collation, you must follow these steps:
1. Apply this software update to the ENTSSO server.
2. Create the SSO database on the instance of SQL Server.
You must apply the update to the ENTSSO server before you use the Configuration Wizard to configure the ENTSSO server.

Note Microsoft BizTalk Server 2004 Service Pack 1 (SP1) also contains an update that adds support for case-sensitive SSO databases for the version of the ENTSSO service that is included with BizTalk Server 2004.

A supported feature that modifies the product's default behavior is now available from Microsoft, but it is only intended to modify the behavior that this article describes. Apply it only to systems that specifically require it. This feature may receive additional testing. Therefore, if the system is not severely affected by the lack of this feature, we recommend that you wait for the next Host Integration Server 2004 service pack that contains this feature.

To obtain this feature immediately, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

The English version of this software update 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 fix that contains these files may also contain additional files.