Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: You cannot log on when FQDN is used and Authentication delegation is set to "Kerberos constrained delegation" in a Forefront Threat Management Gateway 2010 environment

FIX: You cannot log on when FQDN is used and Authentication delegation is set to "Kerberos constrained delegation" in a Forefront Threat Management Gateway 2010 environment

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You publish a web server and authenticate all requests in a Microsoft Forefront Threat Management Gateway 2010 environment.
  • You set Authentication delegation to Kerberos constrained delegation (KCD).
  • You set the Const SE_VPS_VALUE property to 2 to use the fully qualified domain name (FQDN) in the Kerberos ticket as described in the following article:
    960146 An update is available for ISA Server 2006 to control the domain name and user name format in Kerberos Constrained Delegation scenarios
In this scenario, you cannot log on to the web server.

↑ Back to the top

Resolution

To resolve this problem, install the hotfix package that is described in the following Microsoft Knowledge Base article:
2735208 Rollup 3 for Forefront Threat Management Gateway (TMG) 2010 Service Pack 2

↑ Back to the top

Status

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

↑ Back to the top

More Information

By default, TMG 2010 uses the "Domain NETBIOS name\User name" format when it requests a Kerberos ticket. Therefore, the domain name and the user name in the Kerberos ticket resemble the following:
User: FirstName.LastName
Realm: MyCompany
Update 960146 introduced a design change in TMG to control how to format the domain name and the user name by using script.

However, when the Const SE_VPS_VALUE property is set to 2, the FQDN is used for the domain name format. This does not work for users whose name part before the @ sign for the Security Accounts Manager (SAM) account differs from the user principal name (UPN) authentication account.

For example, authentication is successful when SAM and UPN match as follows:
SAM: domain\username 
UPN: username@domain.com
Authentication is unsuccessful when SAM and UPN do not match as follows:
SAM: domain\username
UPN: userUPN@domain.com

↑ Back to the top

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

↑ Back to the top

Keywords: kbnotautohotfix, kbqfe, kbfix, kbexpertiseinter, kbbug, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 2783332
Revision : 1
Created on : 1/7/2017
Published on : 1/10/2013
Exists online : False
Views : 301