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.

Can't sign in to a web application when you use a certificate authentication method in Windows Server 2012 R2


View products that this article applies to.

This article describes an issue that occurs when you use a certificate authentication method in Windows Server 2012 R2. This issue is resolved in the hotfix that’s described in the "Hotfix information" section. This hotfix has a prerequisite.

↑ Back to the top


Symptoms

Consider the following scenario:

  • You have computers that are running Windows Server 2012 R2 in an end-to-end sign-in environment.
  • You use Active Directory Federation Services (AD FS) to identify user access.
  • You configure AD FS to use certificate authentication either for the extranet primary authentication method or as additional Multi-Factor Authentication (MFA).
  • You create a relying party trust by using AD FS.
  • You configure a Security Token Service (STS) proxy and a Web Application Proxy (WAP) in the environment.
  • A client computer tries to sign in to a web application by using the WAP.
In this scenario, the authentication attempt fails, and you cannot sign in.

↑ Back to the top


Resolution

To resolve this issue, install update rollup 2975719, or install the hotfix that is described in this article.

Update information

For more information about how to obtain this update rollup package, click the following article number to view the article in the Microsoft Knowledge Base:
2975719 August 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must first install update 2919355 on Windows Server 2012 R2. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 

2919355 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 Update April, 2014

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 8.1 and Windows Server 2012 R2 file information and notes
Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1/Windows Server 2012 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    VersionProductMilestoneService branch
    6.3.960 0.17xxxWindows Server 2012 R2RTMGDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Microsoft.identityserver.service.dll6.3.9600.17201691,20007-Jun-201411:11x64
Microsoft.identityserver.web.dll6.3.9600.17201809,47207-Jun-201411:11x64
Microsoft.identityserver.dll6.3.9600.17201652,80007-Jun-201411:11x64


↑ 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

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.

Additional file information

Additional file information for Windows Server 20 R2

Additional files for all supported x64-based versions of Windows Server 2012 R2
File propertyValue
File nameAmd64_c55b4bb5e40dead140d01ea312fdf712_31bf3856ad364e35_6.3.9600.17201_none_2a52351d2dc176c5.manifest
File versionNot applicable
File size1,387
Date (UTC)07-Jun-2014
Time (UTC)19:00
PlatformNot applicable
File nameMsil_microsoft.identityserver.service_31bf3856ad364e35_6.3.9600.17201_none_5d4eedd2ffe7b185.manifest
File versionNot applicable
File size3,331
Date (UTC)07-Jun-2014
Time (UTC)13:11
PlatformNot applicable
File nameMsil_microsoft.identityserver.web_31bf3856ad364e35_6.3.9600.17201_none_0d413c96fbe0c0ca.manifest
File versionNot applicable
File size3,315
Date (UTC)07-Jun-2014
Time (UTC)13:11
PlatformNot applicable
File nameMsil_microsoft.identityserver_31bf3856ad364e35_6.3.9600.17201_none_270dc07a762cb1d2.manifest
File versionNot applicable
File size3,299
Date (UTC)07-Jun-2014
Time (UTC)13:11
PlatformNot applicable

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2975066
Revision : 1
Created on : 1/7/2017
Published on : 9/11/2014
Exists online : False
Views : 270