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.
- You publish a website by using Microsoft Forefront Threat Management Gateway (TMG) 2010.
- You configure the Web Listener to use Forms Based Authentication (FBA) with Lightweight Directory Access Protocol (LDAP).
- The LDAP Login Expression is configured to use multiple wildcard characters such as *@contoso*.
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.