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: EnableSharedCookie option doesn't work if the Forefront TMG service runs under a specific account

FIX: EnableSharedCookie option doesn't work if the Forefront TMG service runs under a specific account

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You set up a Microsoft Forefront Threat Management Gateway (TMG) 2010 array that has multiple domain member nodes.
  • You enable the EnableSharedCookie  option to allow for external authenticated users to be handled by all TMG nodes.
  • You configure the TMG firewall service to run as a specific domain account so that internal clients can use the Kerberos protocol to authenticate with the TMG nodes.

In this scenario, you find that external users are prompted unexpectedly for authentication when they are redirected between TMG nodes.

↑ Back to the top

Cause

This problem occurs because Forefront Threat Management Gateway does not use the Domain account for the remote procedure call (RPC) that's used between nodes to exchange user credentials.

↑ Back to the top

Resolution

To resolve this problem, install Rollup 5 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

References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 2965004
Revision : 1
Created on : 1/7/2017
Published on : 6/17/2015
Exists online : False
Views : 218