Article ID: 2654074 - View products that this article applies to.
Consider the following scenario:
In this scenario, the LDAP Login Expression string comparison may become case-sensitive. Then, when a user provides a string such as user@Contoso.com, the string may not match the LDAP Login Expression.
Note This works as expected and is case-insensitive when only one wildcard character is used in the LDAP Login Expression.
This problem occurs because the LDAP Login Expression code incorrectly uses case-sensitive string comparisons when multiple wildcard characters are used.
To resolve this issue, install the hotfix package that is described in the following Microsoft Knowledge Base article:
(http://support.microsoft.com/kb/2649961/ )Rollup 1 for Forefront Threat Management Gateway (TMG) 2010 Service Pack 2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 2654074 - Last Review: January 11, 2012 - Revision: 1.0
Contact us for more help
Connect with Answer Desk for expert help.