AD RMS clients do not authenticate federated identity providers in Windows Server 2008 or in Windows Vista

Article translations Article translations
Article ID: 977624 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You have two partner organizations sharing sensitive data that is protected by using Active Directory Right Management Service (AD RMS).
  • The two organizations have set up a federated relationship. The federated relationship lets users access protected partner resources by using internal identities for authentication.
  • The partner federation server dictates the form of authentication that is required. For example, the server can be configured to require authentication such as forms-based authentication, basic authentication, or Windows Integrated authentication.
In this scenario, the AD RMS client that is running Windows Vista Service Pack 2 (SP2) or Windows Server 2008 Service Pack 2 (SP2) supports only Windows Integrated authentication. The functionality is not interoperable with the usual configuration of the federation servers. Therefore, the protected data cannot be accessed.

Note An application may use an AD RMS client in silent mode. Therefore, the AD RMS client cannot use Windows Internet Explorer to handle authentication when it is required.

RESOLUTION

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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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 Web site:
http://support.microsoft.com/contactus/?ws=support
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, your computer must be running Windows Vista SP2 or Windows Server 2008 SP2. For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:
935791 How to obtain the latest Windows Vista service pack
For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
968849 How to obtain the latest service pack for Windows Server 2008

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 English (United States) 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 Vista and Windows Server 2008 file information notes

Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" 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, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    Collapse this tableExpand this table
    VersionProductSR_LevelService branch
    6.0.600 2 . 22xxxWindows Vista and Windows Server 2008SP2LDR
  • Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008 SP2 and of Windows Vista SP2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Msdrm.dll6.0.6002.22269352,76817-Nov-200912:27x86
Rmactivate_ssp_isv.exe6.0.6002.22135346,62417-Nov-200908:31x86
Secproc_ssp_isv.dll6.0.6002.22269153,08817-Nov-200912:29x86
Rmactivate_isv.exe6.0.6002.22135526,33617-Nov-200908:31Not Applicable
Secproc_isv.dll6.0.6002.22135476,67217-Nov-200912:29x86
Rmactivate_ssp.exe6.0.6002.22135347,13617-Nov-200908:31x86
Secproc_ssp.dll6.0.6002.22269152,57617-Nov-200912:29x86
Rmactivate.exe6.0.6002.22135518,14417-Nov-200908:31Not Applicable
Secproc.dll6.0.6002.22135472,57617-Nov-200912:29x86

For all supported x64-based versions of Windows Server 2008 SP2 and of Windows Vista SP2

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Msdrm.dll6.0.6002.22269486,91217-Nov-200912:21x64
Rmactivate_ssp_isv.exe6.0.6002.22135413,69617-Nov-200908:32x64
Secproc_ssp_isv.dll6.0.6002.22269161,79217-Nov-200912:23x64
Rmactivate_isv.exe6.0.6002.22135600,57617-Nov-200908:32x64
Secproc_isv.dll6.0.6002.22135538,62417-Nov-200912:23x64
Rmactivate_ssp.exe6.0.6002.22135409,60017-Nov-200908:32x64
Secproc_ssp.dll6.0.6002.22269161,79217-Nov-200912:23x64
Rmactivate.exe6.0.6002.22135599,55217-Nov-200908:32x64
Secproc.dll6.0.6002.22135539,13617-Nov-200912:23x64
Msdrm.dll6.0.6002.22269352,76817-Nov-200912:27x86
Rmactivate_ssp_isv.exe6.0.6002.22135346,62417-Nov-200908:31x86
Secproc_ssp_isv.dll6.0.6002.22269153,08817-Nov-200912:29x86
Rmactivate_isv.exe6.0.6002.22135526,33617-Nov-200908:31Not Applicable
Secproc_isv.dll6.0.6002.22135476,67217-Nov-200912:29x86
Rmactivate_ssp.exe6.0.6002.22135347,13617-Nov-200908:31x86
Secproc_ssp.dll6.0.6002.22269152,57617-Nov-200912:29x86
Rmactivate.exe6.0.6002.22135518,14417-Nov-200908:31Not Applicable
Secproc.dll6.0.6002.22135472,57617-Nov-200912:29x86
For all supported IA-64-based versions of Windows Server 2008 SP2

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Msdrm.dll6.0.6002.22269827,90417-Nov-200912:07IA-64
Rmactivate_ssp_isv.exe6.0.6002.22135752,64017-Nov-200908:27IA-64
Secproc_ssp_isv.dll6.0.6002.22269368,64017-Nov-200912:09IA-64
Rmactivate_isv.exe6.0.6002.22135987,64817-Nov-200908:27IA-64
Secproc_isv.dll6.0.6002.22135966,65617-Nov-200912:09IA-64
Rmactivate_ssp.exe6.0.6002.22135750,08017-Nov-200908:27IA-64
Secproc_ssp.dll6.0.6002.22269368,64017-Nov-200912:09IA-64
Rmactivate.exe6.0.6002.22135999,93617-Nov-200908:27IA-64
Secproc.dll6.0.6002.22135970,24017-Nov-200912:09IA-64
Msdrm.dll6.0.6002.22269352,76817-Nov-200912:27x86
Rmactivate_ssp_isv.exe6.0.6002.22135346,62417-Nov-200908:31x86
Secproc_ssp_isv.dll6.0.6002.22269153,08817-Nov-200912:29x86
Rmactivate_isv.exe6.0.6002.22135526,33617-Nov-200908:31Not Applicable
Secproc_isv.dll6.0.6002.22135476,67217-Nov-200912:29x86
Rmactivate_ssp.exe6.0.6002.22135347,13617-Nov-200908:31x86
Secproc_ssp.dll6.0.6002.22269152,57617-Nov-200912:29x86
Rmactivate.exe6.0.6002.22135518,14417-Nov-200908:31Not Applicable
Secproc.dll6.0.6002.22135472,57617-Nov-200912:29x86

STATUS

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

MORE INFORMATION

By default, the AD RMS client operates in silent mode, and user input is not required. The partner federation server may be configured to require user input. For example, the partner federation server may be configured to require forms-based authentication. In this case, the AD RMS client must be configured to ignore the silent mode. The form appears in a browser window and the user is promoted for authentication.

To configure the AD RMS client, include the name of the application in the following AppList registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDRM\Federation
"EnableBrowser"=dword:00000001

"FederationHomeRealm"
=<Home Realm>


A FederationHomeRealm register key is required for the AD RMS client to work in any federation scenario. This is an established requirement. We have included it here for completeness.

The value of the EnableBrowser entry should be set to 1 if the organization wants to use the browser to handle authentication scenarios such as forms based authentication. The setting of the EnableBrowser entry should match the setting of the entry on the federation server.

For example, if the federation server is configured to use forms-based authentication, the FederationHomeRealm registration key is required. If the federation server is configured to use Windows Integrated authentication, this key is not required. You can limit the effect of the Browser key that was discussed earlier in the "More information" section by implicitly listing the applications for which the AD RMS client should always require a browser window. To do this, configure the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDRM\AppList

"
AppList
"=<Semicolon delimited list of applications for which AD RMS client should always show the browser>



For example, Winword.exe, Powerpoint.exe or Excel.exe.

The setting of the EnableBrowser entry should match the setting of the entry on the federation server. For example, if the federation server is configured to use forms-based authentication, this key is required. If the federation server is configured to use Windows Integrated authentication, this key is not required.

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 Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Vista SP2 and of Windows Server 2008 SP2

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Package_1_for_kb977624~31bf3856ad364e35~x86~~6.0.2.0.mumNot Applicable5,07718-Nov-200910:47Not Applicable
Package_2_for_kb977624~31bf3856ad364e35~x86~~6.0.2.0.mumNot Applicable4,91718-Nov-200910:47Not Applicable
Package_for_kb977624_client_2~31bf3856ad364e35~x86~~6.0.2.0.mumNot Applicable1,53018-Nov-200910:47Not Applicable
Package_for_kb977624_client~31bf3856ad364e35~x86~~6.0.2.0.mumNot Applicable1,43118-Nov-200910:47Not Applicable
Package_for_kb977624_server_1~31bf3856ad364e35~x86~~6.0.2.0.mumNot Applicable1,53118-Nov-200910:47Not Applicable
Package_for_kb977624_server~31bf3856ad364e35~x86~~6.0.2.0.mumNot Applicable1,43118-Nov-200910:47Not Applicable
X86_microsoft-windows-r..ement-client-v1-api_31bf3856ad364e35_6.0.6002.22269_none_ea35d635a9b10725.manifestNot Applicable20,37017-Nov-200915:57Not Applicable
X86_microsoft-windows-s..ative-serverbox-isv_31bf3856ad364e35_6.0.6002.22269_none_f74f08e614db5584.manifestNot Applicable5,46617-Nov-200915:59Not Applicable
X86_microsoft-windows-s..native-whitebox-isv_31bf3856ad364e35_6.0.6002.22269_none_eb8a175c06162b6a.manifestNot Applicable5,97417-Nov-200915:56Not Applicable
X86_microsoft-windows-s..or-native-serverbox_31bf3856ad364e35_6.0.6002.22269_none_71f6f8eb7a7e44c9.manifestNot Applicable5,44717-Nov-200915:56Not Applicable
X86_microsoft-windows-s..sor-native-whitebox_31bf3856ad364e35_6.0.6002.22269_none_a32da8c047e49329.manifestNot Applicable5,96417-Nov-200915:56Not Applicable
Additional files for all supported x64-based versions of Windows Vista SP2 and of Windows Server 2008 SP2

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Amd64_microsoft-windows-r..ement-client-v1-api_31bf3856ad364e35_6.0.6002.22269_none_465471b9620e785b.manifestNot Applicable20,41017-Nov-200914:17Not Applicable
Amd64_microsoft-windows-s..ative-serverbox-isv_31bf3856ad364e35_6.0.6002.22269_none_536da469cd38c6ba.manifestNot Applicable5,48617-Nov-200914:20Not Applicable
Amd64_microsoft-windows-s..native-whitebox-isv_31bf3856ad364e35_6.0.6002.22269_none_47a8b2dfbe739ca0.manifestNot Applicable5,99217-Nov-200914:17Not Applicable
Amd64_microsoft-windows-s..or-native-serverbox_31bf3856ad364e35_6.0.6002.22269_none_ce15946f32dbb5ff.manifestNot Applicable5,46717-Nov-200914:15Not Applicable
Amd64_microsoft-windows-s..sor-native-whitebox_31bf3856ad364e35_6.0.6002.22269_none_ff4c44440042045f.manifestNot Applicable5,98217-Nov-200914:15Not Applicable
Package_1_for_kb977624~31bf3856ad364e35~amd64~~6.0.2.0.mumNot Applicable6,31618-Nov-200910:47Not Applicable
Package_2_for_kb977624~31bf3856ad364e35~amd64~~6.0.2.0.mumNot Applicable6,15418-Nov-200910:47Not Applicable
Package_for_kb977624_client_2~31bf3856ad364e35~amd64~~6.0.2.0.mumNot Applicable1,54018-Nov-200910:47Not Applicable
Package_for_kb977624_client~31bf3856ad364e35~amd64~~6.0.2.0.mumNot Applicable1,43918-Nov-200910:47Not Applicable
Package_for_kb977624_server_1~31bf3856ad364e35~amd64~~6.0.2.0.mumNot Applicable1,54118-Nov-200910:47Not Applicable
Package_for_kb977624_server~31bf3856ad364e35~amd64~~6.0.2.0.mumNot Applicable1,43918-Nov-200910:47Not Applicable
X86_microsoft-windows-r..ement-client-v1-api_31bf3856ad364e35_6.0.6002.22269_none_ea35d635a9b10725.manifestNot Applicable20,37017-Nov-200915:57Not Applicable
X86_microsoft-windows-s..ative-serverbox-isv_31bf3856ad364e35_6.0.6002.22269_none_f74f08e614db5584.manifestNot Applicable5,46617-Nov-200915:59Not Applicable
X86_microsoft-windows-s..native-whitebox-isv_31bf3856ad364e35_6.0.6002.22269_none_eb8a175c06162b6a.manifestNot Applicable5,97417-Nov-200915:56Not Applicable
X86_microsoft-windows-s..or-native-serverbox_31bf3856ad364e35_6.0.6002.22269_none_71f6f8eb7a7e44c9.manifestNot Applicable5,44717-Nov-200915:56Not Applicable
X86_microsoft-windows-s..sor-native-whitebox_31bf3856ad364e35_6.0.6002.22269_none_a32da8c047e49329.manifestNot Applicable5,96417-Nov-200915:56Not Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 SP2

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Ia64_microsoft-windows-r..ement-client-v1-api_31bf3856ad364e35_6.0.6002.22269_none_ea377a2ba9af1021.manifestNot Applicable20,38917-Nov-200918:30Not Applicable
Ia64_microsoft-windows-s..ative-serverbox-isv_31bf3856ad364e35_6.0.6002.22269_none_f750acdc14d95e80.manifestNot Applicable5,47517-Nov-200918:32Not Applicable
Ia64_microsoft-windows-s..native-whitebox-isv_31bf3856ad364e35_6.0.6002.22269_none_eb8bbb5206143466.manifestNot Applicable5,98317-Nov-200918:29Not Applicable
Ia64_microsoft-windows-s..or-native-serverbox_31bf3856ad364e35_6.0.6002.22269_none_71f89ce17a7c4dc5.manifestNot Applicable5,45617-Nov-200918:28Not Applicable
Ia64_microsoft-windows-s..sor-native-whitebox_31bf3856ad364e35_6.0.6002.22269_none_a32f4cb647e29c25.manifestNot Applicable5,97317-Nov-200918:28Not Applicable
Package_1_for_kb977624~31bf3856ad364e35~ia64~~6.0.2.0.mumNot Applicable5,97218-Nov-200910:47Not Applicable
Package_for_kb977624_server_1~31bf3856ad364e35~ia64~~6.0.2.0.mumNot Applicable1,37018-Nov-200910:47Not Applicable
Package_for_kb977624_server~31bf3856ad364e35~ia64~~6.0.2.0.mumNot Applicable1,43418-Nov-200910:47Not Applicable
X86_microsoft-windows-r..ement-client-v1-api_31bf3856ad364e35_6.0.6002.22269_none_ea35d635a9b10725.manifestNot Applicable20,37017-Nov-200915:57Not Applicable
X86_microsoft-windows-s..ative-serverbox-isv_31bf3856ad364e35_6.0.6002.22269_none_f74f08e614db5584.manifestNot Applicable5,46617-Nov-200915:59Not Applicable
X86_microsoft-windows-s..native-whitebox-isv_31bf3856ad364e35_6.0.6002.22269_none_eb8a175c06162b6a.manifestNot Applicable5,97417-Nov-200915:56Not Applicable
X86_microsoft-windows-s..or-native-serverbox_31bf3856ad364e35_6.0.6002.22269_none_71f6f8eb7a7e44c9.manifestNot Applicable5,44717-Nov-200915:56Not Applicable
X86_microsoft-windows-s..sor-native-whitebox_31bf3856ad364e35_6.0.6002.22269_none_a32da8c047e49329.manifestNot Applicable5,96417-Nov-200915:56Not Applicable

Properties

Article ID: 977624 - Last Review: December 31, 2009 - Revision: 1.1
APPLIES TO
  • Windows Server 2008 Service Pack 2, when used with:
    • Windows Server 2008 Datacenter without Hyper-V
    • Windows Server 2008 Enterprise without Hyper-V
    • Windows Server 2008 Standard without Hyper-V
    • Windows Server 2008 Datacenter
    • Windows Server 2008 Enterprise
    • Windows Server 2008 Standard
    • Windows Web Server 2008
    • Windows Server 2008 for Itanium-Based Systems
  • Windows Vista Service Pack 2, when used with:
    • Windows Vista Business
    • Windows Vista Enterprise
    • Windows Vista Home Premium
    • Windows Vista Starter
    • Windows Vista Ultimate
    • Windows Vista Home Basic
Keywords: 
kbqfe kbhotfixserver kbsurveynew kbautohotfix kbexpertiseinter kbbug kbfix KB977624

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com