Home realm discovery does not work correctly for a non–claims-aware relying party trust on Windows Server 2012 R2

This article describes an issue that occurs on a Windows Server 2012 R2-based Active Directory Federation Services (AD FS) server. A hotfix is available to resolve this issue. The hotfix has a prerequisite.

Symptoms

Assume that you configure a non–claims-aware relying party trust through a Windows PowerShell command. Then, you publish the relying party trust through Web Application Proxy. In this situation, home realm discovery is not offered correctly, and the non–claims-aware relying party trust is restricted to the Active Directory claims provider trust.

Notes
  • After you install the hotfix, a non–claims aware relying party trust that is created through Windows PowerShell is still restricted to the Active Directory Claims Provider Trust by default. This is to preserve compatibility for people who rely on this behavior.
  • After you install this hotfix, you can specify the ClaimProviderNames parameter during the relying party trust creation to specify which Claims Providers should be offered for the relying party trust.
  • After the relying party trust is created, you can set the ClaimProviderNames parameter to NULL to provide full unfiltered home realm discovery. You cannot set ClaimProviderNames to NULL at creation. You must do this after creation. 
  • If the non–claims-aware relying party trust is created through the AD FS Management console, home realm discovery works and shows all available claims provider trusts.

Resolution

To resolve this issue, we have released a hotfix.

Notes
  • After you install this hotfix, a non–claims-aware relying party trust that is created through a Windows PowerShell command is still restricted to the Active Directory claims provider trust by default. This is to preserve compatibility for people who rely on this behavior.
  • After you install this hotfix, you can specify the ClaimProviderNames parameter during the relying party trust creation to specify which claims providers should be offered for the relying party trust.

Hotfix information

Important If you install a language pack after you install this hotfix, you must reinstall this hotfix. Therefore, we recommend that you install any language packs that you need before you install this hotfix. For more information, see Add language packs to Windows.

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 have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows Server 2012 R2.

Registry information

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

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information

Status

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

References

See the terminology that Microsoft uses to describe software updates.
Properties

Article ID: 3070080 - Last Review: Jul 14, 2015 - Revision: 1

Feedback