使用 Microsoft 登录
登录或创建帐户。
你好,
使用其他帐户。
你有多个帐户
选择要登录的帐户。
英文
很抱歉。本文没有你的语言版本。

Symptoms

Consider the following scenario:

  • 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.

Cause

This problem occurs because the LDAP Login Expression code incorrectly uses case-sensitive string comparisons when multiple wildcard characters are used.

Resolution

To resolve this issue, install the hotfix package that is described in the following Microsoft Knowledge Base article:

2649961 Rollup 1 for Forefront Threat Management Gateway (TMG) 2010 Service Pack 2

Status

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

References

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

需要更多帮助?

需要更多选项?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

此信息是否有帮助?

哪些因素影响了你的体验?
按“提交”即表示你的反馈将用于改进 Microsoft 产品和服务。 你的 IT 管理员将能够收集此数据。 隐私声明。

谢谢您的反馈!

×