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:
http://support.microsoft.com/contactus/?ws=supportNote 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.
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 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:
Version
Product
Milestone
Service branch
6.3.960 0.17xxx
Windows Server 2012 R2
RTM
GDR
-
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 name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Microsoft.identityserver.management.dll |
6.3.9600.17898 |
352,768 |
04-Jun-2015 |
22:27 |
x86 |
|
Microsoft.identityserver.dll |
6.3.9600.17898 |
653,312 |
04-Jun-2015 |
22:27 |
x86 |
Additional file information
Additional file information for Windows Server 2012 R2
Additional files for all supported x64-based versions of Windows Server 2012 R2
|
File property |
Value |
|---|---|
|
File name |
Amd64_9030003dd0a6a465b0ba69377a73e087_31bf3856ad364e35_6.3.9600.17898_none_2c44ef83539ea6a4.manifest |
|
File version |
Not applicable |
|
File size |
708 |
|
Date (UTC) |
06-Jun-2015 |
|
Time (UTC) |
20:09 |
|
Platform |
Not applicable |
|
File name |
Amd64_a76fe17d482bba75c7e4945fdd815dd4_31bf3856ad364e35_6.3.9600.17898_none_90da29f774d65ce3.manifest |
|
File version |
Not applicable |
|
File size |
697 |
|
Date (UTC) |
06-Jun-2015 |
|
Time (UTC) |
20:09 |
|
Platform |
Not applicable |
|
File name |
Msil_microsoft.identityserver.management_31bf3856ad364e35_6.3.9600.17898_none_bfc1874f93bde31d.manifest |
|
File version |
Not applicable |
|
File size |
3,343 |
|
Date (UTC) |
05-Jun-2015 |
|
Time (UTC) |
07:56 |
|
Platform |
Not applicable |
|
File name |
Msil_microsoft.identityserver_31bf3856ad364e35_6.3.9600.17898_none_26b37e98766f4d96.manifest |
|
File version |
Not applicable |
|
File size |
3,299 |
|
Date (UTC) |
05-Jun-2015 |
|
Time (UTC) |
07:56 |
|
Platform |
Not applicable |
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.
